Bug 1995055 - olm.skipRange is not defined
Summary: olm.skipRange is not defined
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Feature Discovery Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.0
Assignee: Carlos Eduardo Arango Gutierrez
QA Contact: Lena Horsley
URL:
Whiteboard:
Depends On:
Blocks: 1995149
TreeView+ depends on / blocked
 
Reported: 2021-08-18 11:22 UTC by Joep van Delft
Modified: 2021-10-18 17:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:19:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-nfd-operator pull 204 0 None None None 2021-08-18 11:23:20 UTC
Red Hat Product Errata RHBA-2021:3760 0 None None None 2021-10-18 17:19:41 UTC

Description Joep van Delft 2021-08-18 11:22:19 UTC
Description of problem:
olm.skipRange is not defined for ART product builds.

Related: https://bugzilla.redhat.com/show_bug.cgi?id=1808420

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Lena Horsley 2021-08-24 17:02:22 UTC
Verified olm.skipRange is correct:
Release branch
https://github.com/openshift/cluster-nfd-operator/blob/release-4.9/manifests/4.9/manifests/node-feature-discovery-operator.clusterserviceversion.yaml


Master branch:
https://github.com/openshift/cluster-nfd-operator/blob/master/manifests/4.9/manifests/node-feature-discovery-operator.clusterserviceversion.yaml


======================================================================================================================================

Successfully created a bundle (latest changes) and deployed the bundle to an AWS cluster consisting of 3 worker and 3 master nodes.
All NFD pods had a status of "Running."

Nodes were properly labeled.

Cluster version: 4.9.0-0.nightly-2021-08-23-224104
Kube version: v1.22.0-rc.0+5c2f7cd

Comment 7 errata-xmlrpc 2021-10-18 17:19:23 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.9 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:3760


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