Bug 1733897
| Summary: | [sriov-operator]Failed to init the VF for mellanox_plugin | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhaozhanqi <zzhao> |
| Component: | Networking | Assignee: | Peng Liu <pliu> |
| Status: | CLOSED ERRATA | QA Contact: | zhaozhanqi <zzhao> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | aos-bugs, cdc |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:33:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Peng Liu
2019-07-29 08:51:53 UTC
mstconfig requires 'rw' permission of sysfs. However in the container, the sysfs is mounted as 'ro'. [root@dell-per740-14 /]# cat /proc/mounts | grep sysfs sysfs /sys sysfs ro,seclabel,nosuid,nodev,noexec,relatime 0 0 sysfs /host/sys sysfs rw,seclabel,nosuid,nodev,noexec,relatime 0 0 sysfs /host/var/lib/containers/storage/overlay/e34d48d94d879727aec1bd4a768535d1ec72f8f20fbc9279ec750254717c2fca/merged/sys sysfs ro,seclabel,nosuid,nodev,noexec,relatime 0 0 This bug is likely cause by this bug https://github.com/cri-o/cri-o/issues/2625 of CRI-O. It should work after the bug fix get merged in downstream CRI-O build. CRI-O fixed has been released in RHCOS build 42.80.20190807.3 Verified this bug on Red Hat Enterprise Linux CoreOS 42.80.20190808.0
- Vfs:
- deviceID: "1018"
driver: vfio-pci
pciAddress: 0000:5e:00.2
vendor: 15b3
- deviceID: "1018"
driver: vfio-pci
pciAddress: 0000:5e:00.3
vendor: 15b3
deviceID: "1017"
driver: mlx5_core
mtu: 1500
name: ens3f0
numVfs: 2
pciAddress: 0000:5e:00.0
totalvfs: 2
vendor: 15b3
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922 |