Bug 1772575

Summary:	The channel name should be string in nfd.package.yaml
Product:	OpenShift Container Platform	Reporter:	Zvonko Kosic <zkosic>
Component:	Node Feature Discovery Operator	Assignee:	Zvonko Kosic <zkosic>
Status:	CLOSED ERRATA	QA Contact:	Walid A. <wabouham>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	anli, mpatel, sejug, wabouham
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1770084	Environment:
Last Closed:	2019-12-11 22:36:10 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:	1770084
Bug Blocks:

Description Zvonko Kosic 2019-11-14 16:32:36 UTC

+++ This bug was initially created as a clone of Bug #1770084 +++

Description of problem:
The channel name is number, it should be string in nfd.package.yaml

cat nfd-o_d6fk02/nfd.package.yaml  
channels:
- currentCSV: nfd.4.2.4-201911050122
  name: 4.2
- currentCSV: nfd.4.3.0-201910250623
  name: '4.3'
defaultChannel: '4.3'
packageName: nfd

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

How reproducible:
Always

Steps to Reproduce:
1.check the channel name in upstream
https://github.com/openshift/cluster-nfd-operator/blob/release-4.2/manifests/olm-catalog/nfd.package.yaml

Actual results:


Expected results:


Additional info:

Comment 1 Zvonko Kosic 2019-11-15 18:06:17 UTC

The link to the master RP: https://github.com/openshift/cluster-nfd-operator/pull/38

Comment 4 Walid A. 2019-12-05 15:50:44 UTC

Verified that the channel name is a string in https://github.com/openshift/cluster-nfd-operator/blob/release-4.2/manifests/olm-catalog/nfd.package.yaml

Comment 6 errata-xmlrpc 2019-12-11 22:36:10 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-2019:4093