Bug 1846239 - [sriov][4.5] Failed to upgrade from 4.4 to 4.5 for sriov operator
Summary: [sriov][4.5] Failed to upgrade from 4.4 to 4.5 for sriov operator
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: All
OS: All
high
urgent
Target Milestone: ---
: 4.5.0
Assignee: Peng Liu
QA Contact: zhaozhanqi
URL:
Whiteboard:
: 1850469 (view as bug list)
Depends On: 1839754
Blocks: 1846241
TreeView+ depends on / blocked
 
Reported: 2020-06-11 07:47 UTC by zhaozhanqi
Modified: 2020-07-13 17:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1839754
: 1846241 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:43:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift sriov-network-operator pull 247 0 None closed [release-4.5] Bug 1846239: Remove required feilds from SriovNetworkNodeState CRD 2020-11-19 14:27:19 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:44:07 UTC

Comment 3 zhaozhanqi 2020-06-19 04:29:34 UTC
Verified this bug on 4.5.0-202006180838 

 oc get csv
NAME                                        DISPLAY                   VERSION              REPLACES                                    PHASE
sriov-network-operator.4.5.0-202006180838   SR-IOV Network Operator   4.5.0-202006180838   sriov-network-operator.4.4.0-202006180922   Succeeded

Comment 4 Petr Horáček 2020-06-24 12:46:52 UTC
*** Bug 1850469 has been marked as a duplicate of this bug. ***

Comment 5 errata-xmlrpc 2020-07-13 17:43: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:2409


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