-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.14.z, 4.15.z, 4.16.z
This is a clone of issue OCPBUGS-38010. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-36683. The following is the description of the original issue:
—
Description of problem:
The 4.16 cluster was deployed using secondary interfaces (Mellanox) with a bond including enslaved VFs.
After SR-IOV operator isntalltion and rebooting, the workers become unreachable because the VFs are not created.
Version-Release number of selected component (if applicable):
4.16.0
sriov-network-operator.v4.16.0-202406200537
How reproducible:
100%
Steps to Reproduce:
1.Install the SR-IOV operator.
2.Reboot.
3.
Actual results:
sh-5.1# mstconfig -d d8:00.0 q | grep SRIOV_EN
SRIOV_EN False(0)
sh-5.1# mstconfig -d d8:00.0 q | grep NUM_OF_VFS
NUM_OF_VFS 0
Expected results:
sh-5.1# mstconfig -d d8:00.0 q | grep SRIOV_EN
SRIOV_EN True(1)
sh-5.1# mstconfig -d d8:00.0 q | grep NUM_OF_VFS
NUM_OF_VFS 5
Additional info:
- blocks
-
OCPBUGS-38525 SR-IOV: SR-IOV operator reset the Mellanox configuration to the default settings
- Closed
- clones
-
OCPBUGS-38010 SR-IOV: SR-IOV operator reset the Mellanox configuration to the default settings
- Closed
- is blocked by
-
OCPBUGS-38010 SR-IOV: SR-IOV operator reset the Mellanox configuration to the default settings
- Closed
- is cloned by
-
OCPBUGS-38525 SR-IOV: SR-IOV operator reset the Mellanox configuration to the default settings
- Closed
- links to
-
RHBA-2024:5750 OpenShift Container Platform 4.15.z extras update