Comment 8 for bug 1917719

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/781612
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/124419ca7a382a9a0eb5dacb9436a0416d5fd513
Submitter: "Zuul (22348)"
Branch: stable/ussuri

commit 124419ca7a382a9a0eb5dacb9436a0416d5fd513
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/+/781611

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