Description of problem: Installation of community NFD operator alpha channel results in a deployment of the controller-manager image from the :latest tag. This image is for a much newer version of the operator, with an update API version for the CRD. This causes a CrashLoopBackoff on the controller-manager and a failed operator installation. Version-Release number of selected component (if applicable): 4.5 on alpha channel How reproducible: always Steps to Reproduce: 1. Install NFD community operator on a stable-4.6 cluster (or any cluster, afaict) (while attempting to work around https://bugzilla.redhat.com/show_bug.cgi?id=1897346 ) from the Operator catalog Actual results: controller-manager pod for NFD operator enters CrashLoopBackoff, logs indicating that nodefeaturediscoveries.nfd.openshift.io/v1 doesn't exist. Verify that CRD installed by bundle is nodefeaturediscoveries.nfd.openshift.io/v1alpha1: https://github.com/openshift/cluster-nfd-operator/blob/release-4.5/manifests/olm-catalog/4.5/nfd.crd.yaml#L39 Verify that Deployment for controller-manager is tracking latest: https://github.com/openshift/cluster-nfd-operator/blob/release-4.5/manifests/olm-catalog/4.5/nfd.v4.5.0.clusterserviceversion.yaml#L162 Expected results: The image in the deployment should use a tag that is pinned to the appropriate version of the operator, registering a watch for v1alpha1. Additional info:
Should a published version of the operator really be targeting the latest tag?
On master branch: make deploy results in the opposite problem. Default image w/ master tag is looking for v1alpha1 CRD, v1 is present. I adjusted the image deployed and all is working as expected, but somehow by default it's wrong.
PR has been merged, this is ready for QA
Now that https://github.com/operator-framework/community-operators/pull/2950 has been merged is this issue still happening, or more fixes are needed thanks
Verified that the community NFD operator can be successfully deployed from OperatorHub on OCP 4.6.0-0.nightly-2021-01-25-060359.
Can confirm that the changes work for deploying to a 3-node 4.6 bare metal cluster from the community catalog. Thanks! Just hoping for 1897346 to clear up soon in support of the official operator release channels.
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 (Moderate: OpenShift Container Platform 4.6.16 extras security 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/RHSA-2021:0310