124419ca7a
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 Added missing change from https://review.opendev.org/c/openstack/tripleo-heat-templates/+/786082 Depends-On: https://review.opendev.org/c/openstack/puppet-tripleo/+/781611 Change-Id: Icef2481b65b41b524ad44eeecfbee4451006e1d2 Closes-Bug: #1917719 (cherry picked from commitdadf71fcae) (cherry picked from commit05b191d3e6)
11 lines
522 B
YAML
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.
|