Failing for installing nodes in a ESX standalone in RHOCP 4

Solution Verified - Updated -

Issue

  • Failing to create an Openshift machine in a standalone ESX Server with the panic error below:

    2022-10-18T10:25:06.331268050Z panic: reflect.Set: value of type mo.ComputeResource is not assignable to type mo.ClusterComputeResource
    
  • When trying to create a OpenShift machine in a standalone ESX server the machine-api-controller podcrashes and fails with the error value of type mo.ComputeResource is not assignable to type mo.ClusterComputeResource`
  • OpenShift machines are always in Provisioning phase and the machine-api-controller pod is restarting

    $ oc get pods -l k8s-app=controller  -n openshift-machine-api
    NAME                                       READY   STATUS    RESTARTS   AGE
    machine-api-controllers-5b5ff45b9b-22wrd   7/7     Running   19         2h9m
    
    $ oc get machines
    NAME                                 PHASE          TYPE   REGION   ZONE   AGE
    example1-worker-8xwmj   Provisioning                          4h45m
    ...
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • UPI VMWARE installation
  • Standalone ESX Server

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content