Comment 9 for bug 1917719

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/781614
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/860a68a4a9e31df4c9224833b094d1ef8173c0f4
Submitter: "Zuul (22348)"
Branch: stable/train

commit 860a68a4a9e31df4c9224833b094d1ef8173c0f4
Author: Martin Schuppert <email address hidden>
Date: Thu Mar 4 08:26:58 2021 +0100

    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

    Added missing change from https://review.opendev.org/c/openstack/tripleo-heat-templates/+/786082

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

    Change-Id: Icef2481b65b41b524ad44eeecfbee4451006e1d2
    Closes-Bug: #1917719
    (cherry picked from commit dadf71fcae73825888b8ed4850de5a6ecf2fc29d)
    (cherry picked from commit 05b191d3e6254fcd6ded4fd8161456f3d5d89632)
    (cherry picked from commit 6c80882f9f52a442400646785def50f5bb8ec4ee)