Comment 0 for bug 1831367

My Rocky tripleo deploy fails - because the network deployment is not correct resulting in a ping failure.

It seems like my config is being ignored particularly the vlan config and subnets from my custom template file: network-environment-overrides.yaml passed on the deploy command line.
The deployed network config data gathered from the deployed nodes after the failed deployment: vlan numbers look like defaults (10 20 30 ..) , not my customised (120 131 132 133..) same with the subnets (compare network-environment-overrides.yaml with controller network info in pastebins)

Some of my console log is attached (watch out for the console control characters in that one) and the output of openstack overcloud failures and my templates folder (all the nic configs are in there but I have selected the single-nic-vlans in network-environment-overrides.yaml).

This is "new", I had this part working last week. What changed? As part of debugging other things I archived my undercloud and started fresh on Thursday (30 May) using almost identical templates.

EXPECTED RESULT: that the vlan tags and subnet ips found when examining nodes match the yaml configs.
Steps to reproduce: Follow tripleos install guide.

Environment: in this case for a 5 node cluster with the undercloud director running in a Centos7 vm.
Logs and configs.
openstack overcloud failures
http://paste.openstack.org/show/752408/

network-environment-overrides.yaml
http://paste.openstack.org/show/752406/

Controller network info (ip r, ip addr, ovs-vsctl show) (other nodes attached but nothing new there)
http://paste.openstack.org/show/752407/

yum list installed (why GitPython.noarch and ansible and more, have suffix -testing?)
http://paste.openstack.org/show/752409/