-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.16
-
Critical
-
No
-
CNF Network Sprint 251
-
1
-
False
-
-
Description of problem:
sriov pod does not launch - SRIOV-CNI failed to load netconf: LoadConf(): VF pci addr is required
Version-Release number of selected component (if applicable):
OCP 4.16 sriov-network-operator.v4.16.0-202403050942
How reproducible:
100%
Steps to Reproduce:
1. Deploy OCP 4.16 SNO via ZTP with sriov-network-operator.v4.16.0-202403050942 2. Launch sriov test pod 3. Check status of test pod
[kni@registry.kni-qe-15 ~]$ oc get pods -n openshift-sriov-network-operator dpdk-testpmd-helix49 NAME READY STATUS RESTARTS AGE dpdk-testpmd-helix49 0/1 ContainerCreating 0 95m
[kni@registry.kni-qe-15 ~]$ oc describe pods -n openshift-sriov-network-operator dpdk-testpmd-helix49 [...] Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 95m default-scheduler Successfully assigned openshift-sriov-network-operator/dpdk-testpmd-helix49 to helix49.ptp.lab.eng.bos.redhat.com Warning FailedCreatePodSandBox 95m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox
Actual results:
pod is stuck at ContainerCreating pod event shows error "ailed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox"
Expected results:
Container is created successfully
Additional info:
- relates to
-
OCPBUGS-30170 Pod stuck in ContainerCreating status - LoadConf(): VF pci addr is required
-
- Closed
-