tripleo-heat-templates/releasenotes/notes/nova_novnc_network-83a1479bf227f867.yaml
Martin Schuppert 05b191d3e6 Use single NovaLibvirtNetwork to configure instance console components
Nova vnc configuration right now uses NovaVncProxyNetwork,
NovaLibvirtNetwork and NovaApiNetwork to configure the different
components (novnc proxy, nova-compute and libvirt) for vnc.
If one of the networks get changed from internal_api, the service
configuration between libvirt, nova-compute and novnc proxy gets
inconsistent and the console is broken.
This changed to just use NovaLibvirtNetwork for configuring the vnc
endpoints and removes NovaVncProxyNetwork completely.

Conflicts:
 deployment/nova/nova-vnc-proxy-container-puppet.yaml

Depends-On: https://review.opendev.org/c/openstack/puppet-tripleo/+/781610

Change-Id: Icef2481b65b41b524ad44eeecfbee4451006e1d2
Closes-Bug: #1917719
(cherry picked from commit dadf71fcae)
2021-03-19 11:05:10 +01:00

11 lines
522 B
YAML

---
fixes:
- |
Nova vnc configuration right now uses NovaVncProxyNetwork, NovaLibvirtNetwork
and NovaApiNetwork to configure the different components (novnc proxy,
nova-compute and libvirt) for vnc. If one of the networks get changed from
internal_api, the service configuration between libvirt, nova-compute and
novnc proxy gets inconsistent and the console is broken.
This changed to just use NovaLibvirtNetwork for configuring the vnc endpoints
and removes NovaVncProxyNetwork completely.