Why does the HyperConverged resource deployment fail?

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

You create the HyperConverged resource for OpenShift Virtualization, but the deployment does not complete successfully.

The HyperConverged configuration might reference node labels or placement settings that do not match your cluster. Red Hat OpenShift on IBM Cloud clusters require you to configure node placement explicitly for infrastructure components and VM workloads.

To resolve the issue,

verify the node labels in your cluster and review the HyperConverged resource configuration.

1. Verify the node labels in your cluster.

   oc get nodes --show-labels
   

2. Check the HyperConverged resource status.

   oc get hyperconverged -n openshift-cnv
   oc describe hyperconverged kubevirt-hyperconverged -n openshift-cnv
   

3. Update the HyperConverged resource with node selectors that match your environment.

   oc edit hyperconverged kubevirt-hyperconverged -n openshift-cnv
   

4. Review the HyperConverged operator logs.

   oc logs -n openshift-cnv -l name=hyperconverged-cluster-operator
   

5. Review the node placement guidance in Installing the OpenShift Virtualization Operator and update the infra and workloads placement settings as needed.