-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17
-
None
-
Moderate
-
None
-
SDN Sprint 264
-
1
-
False
-
-
Description of problem:
After cluster's ungraceful reboot some NNCP resources don't have STATUS:
NAME STATUS REASON for-master-0-intersite Available SuccessfullyConfigured for-master-0-oam Available SuccessfullyConfigured for-master-0-signaling for-master-0-storage Available SuccessfullyConfigured for-worker-1-oam Available SuccessfullyConfigured for-worker-1-signaling for-worker-1-storage Available SuccessfullyConfigured openshift-master-2-bond1-macvlan Available SuccessfullyConfigured openshift-worker-0-bond1-macvlan openshift-worker-1-bond1-macvlan Available SuccessfullyConfigured
Version-Release number of selected component (if applicable):
kubernetes-nmstate-operator.4.17.0-202407261213
How reproducible:
Not always
Steps to Reproduce:
1. Deploy baremetal dualstack cluster with GitOps ZTP
2. Have ACM policies that generate NMSate policies
3. Wait for NMState policies to get into Compliant state
4. Ungraceful reboot cluster
5. Wait for cluster to recover and check NNCP state
Actual results:
Some NNCP resources don't have STATUS set
Expected results:
All NNCP resources are evaluated and have STATUS
- relates to
-
-
- Closed
-
