-
Task
-
Resolution: Done
-
Undefined
-
None
-
CNV v4.18.z
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
test_dhcp_broadcast - both ovs-bridge# and linux-bridge# - fail on all the last 4.18 full-regression runs.
File "/openshift-virtualization-tests/tests/network/l2_bridge/conftest.py", line 385, in started_vmb_dhcp_client run_ssh_commands( File "/openshift-virtualization-tests/.venv/lib/python3.12/site-packages/pyhelper_utils/shell.py", line 123, in run_ssh_commands raise CommandExecFailed(name=" ".join(cmd), err=err) pyhelper_utils.exceptions.CommandExecFailed: Command: sudo nmcli connection up b7e95dda-7746-5bf8-bf33-6e5f3c926790 - exec failed. Error: Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.) Hint: use 'journalctl -xe NM_CONNECTION=b7e95dda-7746-5bf8-bf33-6e5f3c926790 + NM_DEVICE=eth3' to get more details.
It might be that this failure is a result of the IP conflict, that is about to be fixed by https://github.com/RedHatQE/openshift-virtualization-tests/pull/2366. The fact that this job is always executed on a tlv2 cluster, which we already know is affected by the IP conflict, strengthen this assumption. So check if these tests still fail after back-porting this PR to 4.18, preferably on a tlv2 BM cluster.