Comment 18 for bug 1895822

digging some more today - per comment https://bugs.launchpad.net/tripleo/+bug/1895822/comments/8 - there *is* a --control-virtual-ip being passed in both cases afaics

per https://bugs.launchpad.net/tripleo/+bug/1895822/comments/16 as just discussed with sergii on freenode #oooq - I think the env files are the same being passed in both cases?

I agree there is something off about the network config going train->ussuri. We are not getting this bug for ussuri-master jobs - example at [1] which has the 'Ping router ip address' task executed twice (after deploy & after upgrade) without issue.

We changed something train -> ussuri - it might still be related to the switch to 'ha by default' [2].

I've been sanity checking deploy vs upgrade network config but haven't spotted something yet eg [3] vs [4] main diff is

    {"network_config": [{"addresses": [{"ip_netmask": "{{ ctlplane_ip }}/24"}],

vs

    {"network_config": [{"addresses": [{"ip_netmask": "{{ ctlplane_ip }}/24"}, {"ip_netmask": "192.168.24.3/32"}, {"ip_netmask": "192.168.24.1/32"}],

[1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_e30/752419/12/check/tripleo-ci-centos-8-standalone-upgrade/e30bfb8/job-output.txt
[2] https://review.opendev.org/#/c/359060/
[3] https://ac0934616631b7150b73-eba45f55476b984e1cae6ece42d21924.ssl.cf2.rackcdn.com/739457/30/check/tripleo-ci-centos-8-standalone-upgrade-ussuri/3933f4c/logs/undercloud/home/zuul/standalone-ansible-i8z8idi8/Standalone/NetworkConfig
[4] https://ac0934616631b7150b73-eba45f55476b984e1cae6ece42d21924.ssl.cf2.rackcdn.com/739457/30/check/tripleo-ci-centos-8-standalone-upgrade-ussuri/3933f4c/logs/undercloud/home/zuul/standalone-ansible-v1_y03ip/Standalone/NetworkConfig