Bug 2051377 - Unable to switch vfio-pci to netdevice in policy
Summary: Unable to switch vfio-pci to netdevice in policy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Peng Liu
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-07 07:09 UTC by Peng Liu
Modified: 2022-08-10 10:47 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:47:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:47:40 UTC

Description Peng Liu 2022-02-07 07:09:45 UTC
Description of problem:
Unable to change policy from vfio-pci to netdevice. When this is done the config daemon loops infinitely unable to recover.
Changing back to vfio-pci, removing the policy or changing the numVFs fixes this issue.

https://github.com/k8snetworkplumbingwg/sriov-network-operator/issues/244

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


How reproducible:


Steps to Reproduce:
1. Apply a sriovnetworknodepolicy load vfio-pci driver to VFs
2. Update the policy by switching the 'deviceType' from 'vfio-pci' to 'netdevice'
3.

Actual results:
The operator cannot configure the VFs as expected.


Expected results:


Additional info:

Comment 3 zhaozhanqi 2022-04-07 09:44:36 UTC
this bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=2070888

Comment 4 zhaozhanqi 2022-05-07 02:58:56 UTC
Verified this bug on 4.11.0-202205052327

Comment 6 errata-xmlrpc 2022-08-10 10:47:24 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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-2022:5069


Note You need to log in before you can comment on or make changes to this bug.