https://github.com/openshift/cluster-nfd-operator/blob/release-4.6/manifests/olm-catalog/4.6/nfd.v4.6.0.clusterserviceversion.yaml#L34 is pointing to 4.7 should be 4.6
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
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"
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