Comment 2 for bug 1776186

From logs investigation, I think this a legitimate bug/observation.

We do generate an environment-specific network-environment file from

https://github.com/openstack/tripleo-quickstart-extras/blob/master/roles/overcloud-prep-config/templates/network-environment.yaml.j2

and we place it in the /home/{{ undercloud_user }} dir - but in upstream CI, we never use it in the deploy:

## * Deploy the overcloud!
## ::
openstack overcloud deploy \
    --templates /usr/share/openstack-tripleo-heat-templates \
    --libvirt-type qemu --timeout 219 --ntp-server pool.ntp.org -e /home/jenkins/cloud-names.yaml -e /home/jenkins/neutronl3ha.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml -e /home/jenkins/containers-default-parameters.yaml -e /usr/share/openstack-tripleo-heat-templates/ci/environments/network/multiple-nics/network-isolation-absolute.yaml -e /usr/share/openstack-tripleo-heat-templates/ci/environments/network/multiple-nics/network-environment.yaml -e /home/jenkins/overcloud_network_params.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/low-memory-usage.yaml -e /opt/stack/new/tripleo-ci/test-environments/worker-config.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/debug.yaml -e /home/jenkins/enable-tls.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/tls-endpoints-public-ip.yaml -e /home/jenkins/inject-trust-anchor.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml --validation-warnings-fatal --compute-scale 1 --control-scale 3 --ntp-server pool.ntp.org -e /usr/share/openstack-tripleo-heat-templates/ci/environments/ovb-ha.yaml \
    ${DEPLOY_ENV_YAML:+-e $DEPLOY_ENV_YAML} "$@" && status_code=0 || status_code=$?

If we used our own parameter-based customized version, that would be fine, but we create the file and ignore it. As such, the parameterized file pointed to in this bug is probably a better option.