Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1826593

Summary:	[4.4] VF properties are not restored to original values when released from pod
Product:	OpenShift Container Platform	Reporter:	zenghui.shi <zshi>
Component:	Networking	Assignee:	zenghui.shi <zshi>
Networking sub component:	SR-IOV	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	bbennett, zzhao
Version:	4.4
Target Milestone:	---
Target Release:	4.4.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1826592
Clones:	1826595 (view as bug list)		Environment:
Last Closed:	2020-06-02 11:17:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1826592
Bug Blocks:	1771572, 1826595

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