Bug 1916007 - olm skip range is set to the wrong range
Summary: olm skip range is set to the wrong range
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Feature Discovery Operator
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.z
Assignee: Robin Cernin
QA Contact: Walid A.
URL:
Whiteboard:
Depends On: 1916010
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-13 23:07 UTC by Carlos Eduardo Arango Gutierrez
Modified: 2021-03-09 20:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-09 20:00:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-nfd-operator pull 127 0 None closed [release-4.6] Bug 1916007: olm skip range is set to the wrong range 2021-02-25 00:37:40 UTC
Red Hat Product Errata RHBA-2021:0675 0 None None None 2021-03-09 20:00:52 UTC

Comment 2 Robin Cernin 2021-01-19 01:38:45 UTC
Hello Carlos,

It is a valid bug. My understanding is this wouldn't upgrade to 4.1.0-> to 4.7.0, meaning it would miss upgrade in 4.6.z

We saw same issue https://github.com/openshift/cluster-nfd-operator/pull/124/files and the issue comes from mis-understanding of olm.skipRange. 

I can see it's quite simple and has been assigned for a while without PR, hope you don't mind helping you :) 

Created https://github.com/openshift/cluster-nfd-operator/pull/127

Comment 5 Walid A. 2021-03-03 17:34:47 UTC
Verified that https://github.com/openshift/cluster-nfd-operator/blob/release-4.6/manifests/olm-catalog/4.6/nfd.v4.6.0.clusterserviceversion.yaml#L34  now point to version 4.6:

    olm.skipRange: ">=4.3.0 <4.6.0"

Comment 7 errata-xmlrpc 2021-03-09 20:00:46 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 (OpenShift Container Platform 4.6.20 extras 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/RHBA-2021:0675


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