Description of problem: [*] After successful installation on RHV (IPI), the machines in `openshift-machine-api` namespace do not reflect the expected state of the machines, even when all the nodes report Ready state. Version-Release number of selected component (if applicable): v4.8.2 Actual results: [*] Either do not display the status of machines (specifically for master machines), or report the worker nodes still in `provisioned` state. ~~~ oc get machine -n openshift-machine-api -owide NAME PHASE TYPE REGION ZONE AGE NODE PROVIDERID STATE tocpomni-sczzb-master-0 3d22h tocpomni-sczzb-master-1 3d22h tocpomni-sczzb-master-2 3d22h tocpomni-sczzb-worker-8rxkf Provisioned 3d22h tocpomni-sczzb-worker-8rxkf ovirt://xxxx up tocpomni-sczzb-worker-c6m75 Running 3d22h tocpomni-sczzb-worker-c6m75 ovirt://xxxx up tocpomni-sczzb-worker-gps26 Provisioned 3d22h tocpomni-sczzb-worker-gps26 ovirt://xxx up ~~~ [*] All the nodes report to be Ready with IPs assigned: ~~~ $ omg get nodes NAME STATUS ROLES AGE VERSION tocpomni-sczzb-master-0 Ready master 36m v1.21.1+051ac4f tocpomni-sczzb-master-1 Ready master 36m v1.21.1+051ac4f tocpomni-sczzb-master-2 Ready master 36m v1.21.1+051ac4f tocpomni-sczzb-worker-8rxkf Ready worker 24m v1.21.1+051ac4f tocpomni-sczzb-worker-c6m75 Ready worker 26m v1.21.1+051ac4f tocpomni-sczzb-worker-gps26 Ready worker 27m v1.21.1+051ac4f ~~~ [*] The latest yaml definition of the master machines report following status: ~~~ status: conditions: - lastTransitionTime: "2021-08-02T19:53:05Z" message: | Failed to check if machine exists: Failed to parse non-array sso with response <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> reason: ErrorCheckingProvider status: Unknown type: InstanceExists lastUpdated: "2021-08-02T19:53:05Z" phase: "" ~~~ - The RHV console is up and operational as expected. Expected results: [*] After successful installation, all the machines should report expected status. Additional info: [*] Initially, we observed some connection refused messages in the machine's yaml, however, it seems that the connection from machine-api-controller pod is working as expected.
*** This bug has been marked as a duplicate of bug 1989676 ***