OpenShift IPI installation on vSphere fails with: SOAP client: POST "/sdk": 503 Service Unavailable

Solution Verified - Updated -

Issue

  • Cluster installation fails due to DNS misconfiguration

    • OpenShift Worker nodes fails to be provisioned
    $ oc describe machine ocp4-example-worker-0
    <...>
    Status:
      Conditions:
        <...>
        Message: 'Failed to check if machine exists: ocp4-example-worker-0: failed to create scope for machine: failed to create vSphere session: error setting up new vSphere SOAP client: Post "https://vcenter.example.com/sdk": dial tcp 10.0.0.10:443: connect: connection
        Reason:                ErrorCheckingProvider
        Status:                Unknown
        Type:                  InstanceExists
    <...>
    
    • OpenShift Master nodes get successfully deployed but fails to communicate with vCenter APIs
    $ oc describe machine ocp4-example-master-0
    <...>
    Status:
      Conditions:
        <...>
        Message: 'Failed to check if machine exists: ocp4-example-master-0: failed to create scope for machine: failed to create vSphere session: error setting up new vSphere SOAP client: POST "/sdk": 503 Service Unavailable'
    <...>
    

Environment

  • Red Hat OpenShift 4 Cluster on vSphere IPI installation

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