-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.21
-
None
-
None
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
One NNCP on the baremetal cluster stuck in `ConfigurationProgressing` state and it's respective NNCE in `MaxUnavailableLimitReached`:
...
status:
conditions:
- lastHeartbeatTime: "2026-01-22T08:06:30Z"
lastTransitionTime: "2026-01-22T07:39:27Z"
message: Waiting for progressing nodes to finish
reason: MaxUnavailableLimitReached
status: "True"
type: Pending
- lastHeartbeatTime: "2026-01-22T08:06:30Z"
lastTransitionTime: "2026-01-22T07:39:27Z"
reason: MaxUnavailableLimitReached
status: "False"
type: Aborted
- lastHeartbeatTime: "2026-01-22T08:06:30Z"
lastTransitionTime: "2026-01-22T07:39:27Z"
message: Waiting for progressing nodes to finish
reason: MaxUnavailableLimitReached
status: "False"
type: Progressing
- lastHeartbeatTime: "2026-01-22T08:06:30Z"
lastTransitionTime: "2026-01-22T07:39:27Z"
reason: MaxUnavailableLimitReached
status: "False"
type: Failing
- lastHeartbeatTime: "2026-01-22T08:06:30Z"
lastTransitionTime: "2026-01-22T07:39:27Z"
reason: MaxUnavailableLimitReached
status: "False"
type: Available
...
All nodes are in `Ready` state
Version-Release number of selected component (if applicable):
kubernetes-nmstate-operator.4.21.0-202601171823
How reproducible:
So far happened once
Steps to Reproduce:
1. Install and configure baremetal dualstack OCP cluster
2. Configure networking on the nodes with NMState
3. Ungracefully reboot the cluster (power cycle all the node at the same time)
4. One NNCP and NNCE do not report success
Actual results:
The interface on the node seems to be configured correctly(present, IP addresses assigned)
NNCP and NNCE do not report success
Expected results:
NNCP and NNCE are successfully configured
Additional info:
Deleting nmstate-handler and nmstate-operator pods didn't make NNCE progress.
Recreating NNCP did the trick though