tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001 failing with Error: Connection activation failed: No suitable device found for this connection (device ens3 not available because profile is not compatible with device (mismatching interface name)).

[Pooja Jadhav]

tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001 failing with below traceback :

-- Logs begin at Mon 2021-05-03 07:13:19 UTC, end at Mon 2021-05-03 08:09:46 UTC. --
May 03 07:14:28 overcloud-controller-0 systemd[1]: Starting LSB: Bring up/down networking...
May 03 07:14:28 overcloud-controller-0 network[1219]: WARN : [network] You are using 'network' service provided by 'network-scripts', which are now deprecated.
May 03 07:14:28 overcloud-controller-0 network[1219]: WARN : [network] 'network-scripts' will be removed in one of the next major releases of RHEL.
May 03 07:14:28 overcloud-controller-0 network[1219]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network management.
May 03 07:14:28 overcloud-controller-0 network[1219]: Bringing up loopback interface: [ OK ]
May 03 07:14:28 overcloud-controller-0 network[1219]: Bringing up interface ens3: [ OK ]
May 03 07:14:28 overcloud-controller-0 network[1219]: Bringing up interface eth0: Error: Connection activation failed: No suitable device found for this connection (device ens3 not available because profile is not compatible with device (mismatching interface name)).
May 03 07:14:28 overcloud-controller-0 network[1219]: [FAILED]
May 03 07:14:28 overcloud-controller-0 systemd[1]: network.service: Control process exited, code=exited status=1
May 03 07:14:28 overcloud-controller-0 systemd[1]: network.service: Failed with result 'exit-code'.
May 03 07:14:28 overcloud-controller-0 systemd[1]: Failed to start LSB: Bring up/down networking.
-- Logs begin at Mon 2021-05-03 07:13:19 UTC, end at Mon 2021-05-03 08:09:46 UTC. --
May 03 07:13:28 overcloud-controller-0 systemd[1]: Starting Network Manager Wait Online...
May 03 07:14:28 overcloud-controller-0 systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=1/FAILURE
May 03 07:14:28 overcloud-controller-0 systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'.
May 03 07:14:28 overcloud-controller-0 systemd[1]: Failed to start Network Manager Wait Online.

References :

https://logserver.rdoproject.org/31/789131/2/openstack-check/tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001/a71b64c/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz

https://logserver.rdoproject.org/31/789131/2/openstack-check/tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001/a71b64c/logs/overcloud-controller-0/var/log/extra/failed_services.txt.gz

[Sagi (Sergey) Shnaidman (sshnaidm)]

Shouldn't it be solved by https://review.opendev.org/c/openstack/tripleo-image-elements/+/769209 ?

[wes hayutin (weshayutin)]

same message can be seen in passing runs.
https://logserver.rdoproject.org/31/789131/4/openstack-check/tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001/048e4db/logs/overcloud-controller-0/var/log/extra/failed_services.txt.gz

The diff afaict.. is that the overcloud controller in passing case, ( always look to compare against a pssing case ) is that the interfaces got ip addresses.
https://logserver.rdoproject.org/31/789131/4/openstack-check/tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001/048e4db/logs/overcloud-controller-0/var/log/extra/network.txt.gz

vs...

Failing case..

https://logserver.rdoproject.org/31/789131/2/openstack-check/tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001/a71b64c/logs/overcloud-controller-0/var/log/extra/network.txt.gz

Issue was probably infra related.

[Rabi Mishra (rabi)]

Though this is not blocking, I think there is still an issue with the image and should be fixed.

Probably get rid of /etc/sysconfig/network-scripts/ifcfg-eth0 from the image.