26fbc01f53
In Debian, SPICE is the default. Unfortunately, puppet-openstack fails to set [spice]/enabled = false when VNC is selected, and therefore, both VNC and SPICE ends up being enabled in nova.conf. Also, Debian has a unique package nova-consoleproxy handling SPICE, VNC and the XenVNC console, with /etc/default/nova-consoleproxy being used to select what daemon to start. As puppet-openstack doesn't set it before starting the VNC console service, it stays with spicehtml5 as default value, and therefore, nova-novncproxy cannot start. This patch fixes both issues. Change-Id: Ia40805f27e8833fa01576432ae792e1becedd729
14 lines
590 B
YAML
14 lines
590 B
YAML
---
|
|
features:
|
|
- |
|
|
Puppet-openstack now manages both [vnc]/enabled and [spice]/enabled. This
|
|
was needed because Debian has [spice]/enabled set to True by default, and
|
|
one cannot have both enabled in a compute node. Therefore, it was mandatory
|
|
to have [spice]/enabled set to Flase if we're using VNC.
|
|
upgrade:
|
|
- |
|
|
Users of puppet-openstack will have to set ::nova::compute::spice_enabled to
|
|
True to make a meaningful decisioin to use Spice and not use VNC, and not
|
|
rely on ::nova::spicehtml5proxy or ::nova::compute::spice to set it as
|
|
enabled by default.
|