-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
4
-
None
-
None
-
None
-
None
-
CNF Network Sprint 271, CNF Network Sprint 272
-
2
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
After removing a SriovNetworkNodePolicy, the SR-IOV operator becomes stuck in the "In Progress" state. No further progress is observed, and the expected reconciliation or clean-up process does not complete. Additionally, no relevant logs are generated beyond the point of deletion, making it difficult to troubleshoot.
Version-Release number of selected component (if applicable):
- ARM
- SNO
- BF3
- 4.19.0-0.nightly-multi-2025-05-13-043339
- sriov-network-operator.v4.19.0-202505121540
How reproducible:
70%
Steps to Reproduce:
1. run conformance SR-IOV tests https://github.com/openshift/sriov-network-operator/tree/main/test/conformance
2.
3.
Actual results:
$ oc get sriovnetworknodestates.sriovnetwork.openshift.io -A
NAMESPACE NAME SYNC STATUS DESIRED SYNC STATE CURRENT SYNC STATE AGE
openshift-sriov-network-operator cnfdg44.ptp.eng.rdu2.dc.redhat.com InProgress Idle Idle 3d23h
Expected results:
$ oc get sriovnetworknodestates.sriovnetwork.openshift.io -A NAMESPACE NAME SYNC STATUS DESIRED SYNC STATE CURRENT SYNC STATE AGE openshift-sriov-network-operator cnfdg44.ptp.eng.rdu2.dc.redhat.com Succeeded Idle Idle 3d23h
Additional info:
must-gather: https://drive.google.com/file/d/15XH7MJ3EfFi9RTNAaSBDYHvypT9qp_Z9/view?usp=sharing
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to