Why does the OpenShift Virtualization Operator installation fail?

Virtual Private Cloud 4.17 and later Bare metal worker nodes only RHCOS only

You try to install the OpenShift Virtualization Operator, but the installation does not complete successfully.

The cluster is not fully prepared for the operator installation. Common causes include disabled default catalog sources, outbound traffic protection that blocks required access, or a failed subscription in the openshift-cnv namespace.

To resolve the issue,

verify the catalog sources, outbound traffic protection setting, and operator subscription.

1. Verify that the default catalog sources are enabled.

   oc get catalogsource -n openshift-marketplace
   

2. If catalog sources are not listed, enable them.

   oc patch operatorhub cluster --type json -p '[{"op": "add", "path": "/spec/disableAllDefaultSources", "value": false}]'
   

3. Check whether outbound traffic protection is enabled.

   ibmcloud oc vpc outbound-traffic-protection get -c <cluster_name>
   

4. If outbound traffic protection is enabled, disable it.

   ibmcloud oc vpc outbound-traffic-protection disable -c <cluster_name>
   

5. Review the operator subscription status.

   oc get subscription -n openshift-cnv
   oc describe subscription hco-operatorhub -n openshift-cnv
   

6. Review the operator logs for errors.

   oc logs -n openshift-cnv -l app=kubevirt-hyperconverged-operator
   

7. If the operator still does not install, review Installing the OpenShift Virtualization Operator and collect the command output before you contact IBM Cloud support.