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

Bug 1808420

Summary:	OCP 4.4: Node Feature Discover (NFD) - olm.skipRange and minKubeVersion are not specified in the nfd clusterserviceversion.yaml
Product:	OpenShift Container Platform	Reporter:	Zvonko Kosic <zkosic>
Component:	Node Feature Discovery Operator	Assignee:	Carlos Eduardo Arango Gutierrez <carangog>
Status:	CLOSED ERRATA	QA Contact:	Walid A. <wabouham>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	carangog, mifiedle, sejug
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:22:21 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:
Bug Blocks:	1804889

Description Zvonko Kosic 2020-02-28 13:45:17 UTC

This bug was initially created as a copy of Bug #1804889

I am copying this bug because: 



Description of problem:
The olm.skipRange and minKubeVersion variables are missing in the nfd clusterserviceversion.yaml :

https://github.com/openshift/cluster-nfd-operator/blob/master/manifests/olm-catalog/4.4/nfd.v4.4.0.clusterserviceversion.yaml

minKubeVersion is the minimal KubeVersion required by your Operator.

olm.skipRange is the scope from which your clusterserviceversion can be upgraded from.

Thanks to Anping Li for bringing this to our attention.

Version-Release number of selected component (if applicable):
https://github.com/openshift/cluster-nfd-operator master, release-4.3 branches

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Mike Fiedler 2020-03-04 22:24:42 UTC

The file on the 4.5 branch is named nfd.v4.4.0.clusterserviceversion.yaml

@carangog Should the file be nfd.v4.5.0.clusterserviceversion.yaml?

Comment 5 Carlos Eduardo Arango Gutierrez 2020-03-04 22:28:34 UTC

It does have to be, will patch ASAP

Comment 6 Mike Fiedler 2020-03-04 22:30:53 UTC

Also, should the skip range be 1 version higher than the 4.4 version of the fix?   https://github.com/openshift/cluster-nfd-operator/pull/72/files

Comment 7 Carlos Eduardo Arango Gutierrez 2020-03-05 13:19:15 UTC

PR -> https://github.com/openshift/cluster-nfd-operator/pull/75

Comment 9 Zvonko Kosic 2020-03-09 15:21:24 UTC

(In reply to Mike Fiedler from comment #4)
> The file on the 4.5 branch is named nfd.v4.4.0.clusterserviceversion.yaml
> 
> @carangog Should the file be nfd.v4.5.0.clusterserviceversion.yaml?

We need to address this ^^ comment first. Setting to POST.

Comment 12 Walid A. 2020-06-23 16:15:52 UTC

Verified minKubeVersion, olm.skipRange  and crd name are now correct:

https://github.com/openshift/cluster-nfd-operator/blob/release-4.5/manifests/olm-catalog/4.5/nfd.v4.5.0.clusterserviceversion.yaml
and
https://github.com/openshift/cluster-nfd-operator/blob/master/manifests/olm-catalog/4.5/nfd.v4.5.0.clusterserviceversion.yaml

Comment 14 errata-xmlrpc 2020-07-13 17:22:21 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