Bug 2056343 - [4.6] SRIOV exclusive pooling
Summary: [4.6] SRIOV exclusive pooling
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.z
Assignee: Balazs Nemeth
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 2056342
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-21 03:43 UTC by zenghui.shi
Modified: 2023-09-15 01:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2056342
Environment:
Last Closed: 2022-09-09 05:15:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-device-plugin pull 56 0 None open Bug 2056343: exclusive pool 2022-08-12 01:00:59 UTC
Red Hat Product Errata RHSA-2022:6262 0 None None None 2022-09-09 05:15:33 UTC

Comment 1 zhaozhanqi 2022-07-20 03:37:29 UTC
do we still need to backport to 4.6 version. Not sure if any customer still using 4.6 version?

Comment 2 Balazs Nemeth 2022-07-29 08:53:17 UTC
@evadla

Based on https://bugzilla.redhat.com/show_bug.cgi?id=1997650, it seems that the customer was using 4.6. Is this still true?

Comment 5 zhaozhanqi 2022-09-07 08:19:04 UTC
Verified this bug on sriov-network-operator.4.6.0-202208241715

Comment 7 errata-xmlrpc 2022-09-09 05:15:05 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.6.61 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:6262

Comment 8 Red Hat Bugzilla 2023-09-15 01:52:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


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