-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.13, 4.12
-
Important
-
No
-
CNF Network Sprint 242
-
1
-
False
-
-
-
This is a clone of issue OCPBUGS-16246. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-5892. The following is the description of the original issue:
—
Description of problem:
Creating a pod with vf takes up to 2 minutes. Warning FailedCreatePodSandBox 4s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_testpod-br2rg_sriov-operator-tests_cd1295e2-bc1f-46a9-b5fb-538c94ed2e48_0(de9ffb0385fd56d085434588f03d24f756e5f5bbae0f8b3b0d522f1ee1483b59): error adding pod sriov-operator-tests_testpod-br2rg to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [sriov-operator-tests/testpod-br2rg/cd1295e2-bc1f-46a9-b5fb-538c94ed2e48:test-sriov-static-usual]: error adding container to network "test-sriov-static-usual": SRIOV-CNI failed to load netconf: LoadConf(): the VF 0000:86:01.0 does not have a interface name or a dpdk driver
Version-Release number of selected component (if applicable):
Intel nic E810 4.12.0-rc.8 sriov-network-operator.v4.12.0-202301062016
How reproducible:
25%
Steps to Reproduce:
1.Create sriov network policies with 64 VF 2.Create a pod with 1 VF 3.Delete the pod 4.Create the pod again
Actual results:
Creating a pod with vf takes up to 2 minutes.
Expected results:
Creating a pod with vf takes up to 10 sec.
Additional info:
There is no the issue on e710 and metllanox nics
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
-
RHBA-2023:5389
OpenShift Container Platform 4.12.z bug fix update