Bug 1789564

Summary:	Failed to allocate a SRIOV VF to VMI
Product:	Container Native Virtualization (CNV)	Reporter:	sgott
Component:	Networking	Assignee:	Petr Horáček <phoracek>
Status:	CLOSED ERRATA	QA Contact:	Yan Du <yadu>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.2.0	CC:	cnv-qe-bugs, danken, fdeutsch, ipinto, myakove, phoracek
Target Milestone:	---
Target Release:	2.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virt-operator-container-v2.3.0-30 hco-bundle-registry-container-v2.2.0-363	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-28 19:09:38 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:

Description sgott 2020-01-09 20:05:32 UTC

Description of problem:
Subsequent to the stable branch for CNV 2.2.0 being created an selinux issue affecting SRIOV was noted and fixed: https://github.com/kubevirt/kubevirt/issues/2887

with the PR here: https://github.com/kubevirt/kubevirt/issues/2887

This was never backported. Without this, SRIOV devices cannot be allocated in VMIs when using SELinux.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 sgott 2020-01-09 20:14:59 UTC

Correct URL to PR is:

https://github.com/kubevirt/kubevirt/issues/2888

Comment 4 Fabian Deutsch 2020-01-14 16:10:16 UTC

Moving this back to assigned, as the current patch does not address the issue on RHCOS

Comment 5 sgott 2020-02-17 12:52:56 UTC

These two PRs enable a workaround for this:

https://github.com/kubevirt/kubevirt/pull/3056
https://github.com/kubevirt/hyperconverged-cluster-operator/pull/445

Comment 6 sgott 2020-02-19 17:10:09 UTC

To verify: ensure virt-launcher pod runs as spc_t when deployed via HCO

Comment 13 Dan Kenigsberg 2020-03-05 19:07:48 UTC

Stu, this bug has patches fixing it. Are they in 2.2.0?

Comment 14 sgott 2020-03-05 19:15:13 UTC

No, they are not.

Comment 18 Petr Horáček 2020-04-16 15:25:43 UTC

This should be now fixed. We can verify it as soon as we have SR-IOV cluster set up.

Comment 19 Yan Du 2020-04-17 06:53:56 UTC

we don't have an available SR-IOV cluster for now, will verify the bug once get the SR-IOV cluster.

Comment 20 Yan Du 2020-05-15 07:03:41 UTC

Test on OCP4.4 CNV2.3
Client Version: 4.4.3
Server Version: 4.4.0-rc.13
Kubernetes Version: v1.17.1

SR-IOV network can be attached to the VM, didn't see any selinux permission error in virt-launcher when selinux is enabled

Comment 23 errata-xmlrpc 2020-07-28 19:09:38 UTC

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/RHSA-2020:3194