-
Bug
-
Resolution: Unresolved
-
Critical
-
4.17.z, 4.16.z, 4.18.z, 4.19.z, 4.20.0, 4.21.0
Description of problem:
The NMState service is failing in some OCP deployments. This seems to be a recent change caused by a new dependency on NetworkManager-wait-online, which often fails in baremetal deployments (and possibly other on-prem environments with multiple NICs).
- systemctl status nmstate
○ nmstate.service - Apply nmstate on-disk state
Loaded: loaded (/usr/lib/systemd/system/nmstate.service; enabled; preset: enabled)
Active: inactive (dead)
Docs: man:nmstate.service(8)
https://www.nmstate.io
Sep 12 21:19:43 master-0 systemd[1]: Dependency failed for Apply nmstate on-disk state.
Sep 12 21:19:43 master-0 systemd[1]: nmstate.service: Job nmstate.service/start failed with result 'dependency'.
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Seems to always reproduce in dev-scripts environments.
Steps to Reproduce:
1. Configure to deploy with NMState managing br-ex 2. 3.
Actual results:
Deployment fails due to br-ex configuration not being applied.
Expected results:
Additional info:
- blocks
-
CNV-61818 Regression testing for 4.20.0
-
- In Progress
-
-
OCPBUGS-61824 NMState service failing in some deployments
-
- Verified
-
-
CNV-62607 Upgrade test : EUS upgrade from 4.18 to 4.20
-
- In Progress
-
-
CNV-66167 Upgrade test : Upgrade from 4.19 to 4.20
-
- In Progress
-
- is blocked by
-
CORENET-6419 Impact NMState service failing in some deployments
-
- Closed
-
- is caused by
-
RHEL-114959 nmstate fails in systems with NetworkManager-wait-online timeout
-
- Release Pending
-
- is cloned by
-
OCPBUGS-61824 NMState service failing in some deployments
-
- Verified
-
- links to