-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.12
-
Important
-
3
-
Sprint 231 - Team OSInt, Sprint 232 - Team OSInt
-
2
-
Rejected
-
False
-
Description of problem:
CI job has failed twice due to DHCP failures
periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-stable-azure-ipi-disconnected-fullyprivate
NetworkManager[1411] <info> [1672699601.8899] dhcp4 (br-ex): canceled DHCP transaction NetworkManager[1411] <info> [1672699601.8901] device (br-ex): released from master device br-ex NetworkManager[1411] <warn> [1672699601.8903] device (br-ex): Activation: failed for connection 'ovs-if-br-ex' NetworkManager[1411] <info> [1672699601.8910] device (br-ex): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') NetworkManager[1411] <info> [1672699601.8914] device (br-ex): state change: disconnected -> unmanaged (reason 'user-requested', sys-iface-state: 'managed') ERROR: Cannot bring up connection ovs-if-br-ex after 10 attempts
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-arm64-2023-01-02-175115
How reproducible:
2 times
Steps to Reproduce:
1. periodic-ci-openshift-openshift-tests-private-release-4.12-arm64-stable-azure-ipi-disconnected-fullyprivate-p2-f14 2. 3.
Actual results:
DHCP fails on one master, OVN pod fails in CrashLoopBackOff
ERROR: Cannot bring up connection ovs-if-br-ex after 10 attempts
Expected results:
Successful install
Additional info:
Failed jobs
Failed syslogs
[OCPQE-13424]
- depends on
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- links to