Comment 1 for bug 1917719

the issue is that we have NovaVncProxyNetwork [1], NovaLibvirtNetwork [2] and NovaApiNetwork [3] being used for vnc configuration. We should move to use one network for vnc configuration, probably the NovaLibvirtNetwork as this is also used in couple of places, e.g. live migration. 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 as seen from the tempest test.

[1] https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/nova/nova-compute-container-puppet.yaml#L1102
[2] https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/nova/nova-libvirt-container-puppet.yaml#L441
[3] https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/nova/nova-vnc-proxy-container-puppet.yaml#L256