Description of problem: Overcloud deployment with ML2/OVS network backend + DVR fails complaining on missing net_config_bridge.j2 2022-01-03 19:51:29.921 136583 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Exception occured while running the command: heatclient.exc.CommandError: Could not fetch contents for file:///home/stack/overcloud-deploy/overcloud/tripleo-heat-templates/environments/templates/net_config_bridge.j2 2022-01-03 19:51:29.921 136583 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud Traceback (most recent call last): 2022-01-03 19:51:29.921 136583 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib64/python3.6/urllib/request.py", line 1505, in open_local_file 2022-01-03 19:51:29.921 136583 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud stats = os.stat(localfile) 2022-01-03 19:51:29.921 136583 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud FileNotFoundError: [Errno 2] No such file or directory: '/home/stack/overcloud-deploy/overcloud/tripleo-heat-templates/environments/templates/net_config_bridge.j2' Please find overcloud_deploy.sh script below [1] The script has reference to /usr/share/openstack-tripleo-heat-templates/environments/neutron-ovs-dvr.yaml file which contains following lines: # With using default template values, the Compute nodes also need the br-ex # bridge to be connected to a physical network. ComputeNetworkConfigTemplate: 'templates/net_config_bridge.j2' However during rendering j2 templates to files under /home/stack/overcloud-deploy/overcloud/tripleo-heat-templates/ the templates/net_config_bridge.j2 is not found. Note: DVR is the default configuration, so the issue should be fixed ASAP. Version-Release number of selected component (if applicable): RHOS-17.0-RHEL-8-20211208.n.1 How reproducible: 100% Steps to Reproduce: 1. Try to deploy OSP17 environment with ML2/OVS network backend + DVR Actual results: Overcloud deploy fails due to missing net_config_bridge.j2 during rendering j2 templates Expected results: Overcloud deploy succeeds Additional info: [1] overcloud_deploy.sh script #!/bin/bash openstack overcloud deploy \ --timeout 100 \ --templates /usr/share/openstack-tripleo-heat-templates \ --stack overcloud \ --libvirt-type kvm \ --ntp-server clock1.rdu2.redhat.com \ --deployed-server \ -e /home/stack/templates/overcloud-vip-deployed.yaml \ -e /home/stack/templates/overcloud-networks-deployed.yaml \ -e /home/stack/templates/overcloud-baremetal-deployed.yaml \ --disable-protected-resource-types \ --networks-file /home/stack/virt/network/network_data_v2.yaml \ -e /home/stack/virt/config_lvm.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/neutron-ovs-dvr.yaml \ -e /home/stack/virt/network/network-environment_v2.yaml \ -e /home/stack/virt/enable-tls.yaml \ -e /home/stack/virt/inject-trust-anchor.yaml \ -e /home/stack/virt/public_vip.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-ip.yaml \ -e /home/stack/virt/hostnames.yml \ -e /home/stack/virt/debug.yaml \ -e /home/stack/virt/config_heat.yaml \ -e /home/stack/virt/nodes_data.yaml \ -e ~/containers-prepare-parameter.yaml \ -e /home/stack/virt/nova-resize-on-the-same-host.yaml \ -e /home/stack/virt/dns.yaml \ -e /home/stack/virt/l3_fip_qos.yaml \ -e /home/stack/virt/floating_ip_port_forwarding.yaml \ -e /home/stack/virt/set-nova-scheduler-filter.yaml \ --log-file overcloud_deployment_44.log
See this job that uses ML2OVS + DVR has deployed sucessfully in Phase3: https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/DFG/view/network/view/neutron/job/DFG-network-neutron-17.0_director-rhel-virthost-3cont_2comp-ml2ovs-ipv4-vxlan-tobiko-tempest-dvr/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543