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:
(In reply to Anping Li from comment #0) > 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: How can we test this on a running cluster? What were your steps to find this bug? What effect does it have when the version number is not a string?
Verified that the channel name is a string in: https://github.com/openshift/cluster-nfd-operator/blob/release-4.3/manifests/olm-catalog/nfd.package.yaml
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:0062