Comment 1 for bug 1991660

I am not 100% sure, but we have task:

2022-10-04 12:24:06.953686 | primary | TASK [Add eth2 interface from eth2.conf] ***************************************
2022-10-04 12:24:06.953712 | primary | Tuesday 04 October 2022 12:24:06 +0000 (0:00:00.052) 0:07:10.718 *******
2022-10-04 12:24:15.045581 | primary | changed: [undercloud]

This I belive should set 10.0.0.1/24 on eth2 on the undercloud. Looking at log[1] eth2 has no address. It is however configured in network-scripts with 10.0.0.1.

This is what the journal on the undercloud logs related to that task:

Oct 04 12:24:08 node-0003111047 ansible-ansible.legacy.command[72162]: Invoked with _raw_params=os-net-config -c /home/zuul/eth2.conf -v _uses_shell=False warn=False stdin_add_newline=True strip_empty_ends=True argv=None chdir=None executable=None creates=None removes=None stdin=None
Oct 04 12:24:09 node-0003111047 ifdown[72172]: You are using 'ifdown' script provided by 'network-scripts', which are now deprecated.
Oct 04 12:24:09 node-0003111047 ifdown[72173]: 'network-scripts' will be removed from distribution in near future.
Oct 04 12:24:09 node-0003111047 ifdown[72174]: It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.3584] device (eth2): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 04 12:24:09 node-0003111047 ifup[72231]: You are using 'ifup' script provided by 'network-scripts', which are now deprecated.
Oct 04 12:24:09 node-0003111047 ifup[72232]: 'network-scripts' will be removed from distribution in near future.
Oct 04 12:24:09 node-0003111047 ifup[72233]: It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4719] device (eth2): carrier: link connected
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4726] device (eth2): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4745] policy: auto-activating connection 'Wired connection 2' (9db43117-3135-37cf-9ee1-8ceece888f45)
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4753] device (eth2): Activation: starting connection 'Wired connection 2' (9db43117-3135-37cf-9ee1-8ceece888f45)
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4754] device (eth2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4759] device (eth2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4766] device (eth2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 04 12:24:09 node-0003111047 NetworkManager[789]: <info> [1664886249.4773] dhcp4 (eth2): activation: beginning transaction (timeout in 45 seconds)
Oct 04 12:24:12 node-0003111047 ipv6_wait_tentative[72292]: Waiting for interface eth2 IPv6 address(es) to leave the 'tentative' state
Oct 04 12:24:13 node-0003111047 ipv6_wait_tentative[72297]: Waiting for interface eth2 IPv6 address(es) to leave the 'tentative' state

NetworkManager is trying to use dhcp4 on (eth2) there, I get the feeling that there may be some conflict with NM connection 'Wired connection 2' causing troubles.

[1] https://logserver.rdoproject.org/82/44982/6/check/periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset064-master/3fac403/logs/undercloud/var/log/extra/network.txt.gz
[2] https://logserver.rdoproject.org/82/44982/6/check/periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset064-master/3fac403/logs/undercloud/etc/sysconfig/network-scripts/ifcfg-eth2.gz