Bug 1826593 - [4.4] VF properties are not restored to original values when released from pod
Summary: [4.4] VF properties are not restored to original values when released from pod
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.z
Assignee: zenghui.shi
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 1826592
Blocks: 1771572 1826595
TreeView+ depends on / blocked
 
Reported: 2020-04-22 03:52 UTC by zenghui.shi
Modified: 2020-06-02 11:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1826592
: 1826595 (view as bug list)
Environment:
Last Closed: 2020-06-02 11:17:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-cni pull 17 0 None closed BUG 1826593: Restore original VF value when needed (#114) 2020-07-06 07:02:03 UTC
Red Hat Product Errata RHBA-2020:2310 0 None None None 2020-06-02 11:18:29 UTC

Description zenghui.shi 2020-04-22 03:52:48 UTC
+++ This bug was initially created as a clone of Bug #1826592 +++

Description of problem:

When a VF device is released from Pod, SR-IOV CNI always set VF properties to a fixed default values which may not be correct for devices from different vendors.


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

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 zhaozhanqi 2020-05-25 10:07:01 UTC
Verified this bug on 4.4.0-202005221118

Delete and create policy at same time, the new create policy works well.

Comment 6 zhaozhanqi 2020-05-25 10:26:02 UTC
please ignore comment 5. typo

verified step should be from https://bugzilla.redhat.com/show_bug.cgi?id=1826592#c3

Comment 8 errata-xmlrpc 2020-06-02 11:17:50 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/RHBA-2020:2310


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