vSphere ABI wait for install command has been successful even though some operators are in progressing state. The command should be failed with timeout issue as the progressing operators can not be successful due to vSphere authentication issue.

4.13

Always

1. Create agent.iso and boot it on vSphere vm.
2. Execute openshift-install agent wait-for install-complete --log-level debug
3. Execute oc get co to check the operators status

Wait for install complete is successful and some operators are in progressing state.

DEBUG Still waiting for the cluster to initialize: Cluster operators authentication, monitoring are not available 
INFO Cluster is installed                         
INFO Install complete!                            
INFO To access the cluster as the system:admin user when using 'oc', run 
INFO     export KUBECONFIG=/home/mhans/compact/auth/kubeconfig 
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.mhans-compact.qe.devcluster.openshift.com 
INFO Login to the console with user: "kubeadmin", and password: "XXXX-XXXX-XXXX-XXXX" 


oc get co openshift-apiserver storage etcd authentication kube-apiserver 
NAME                  VERSION       AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
openshift-apiserver   4.13.0-0.nightly-2023-03-29-235439   True        True          False      110s    APIServerDeploymentProgressing: deployment/apiserver.openshift-apiserver: 1/3 pods have been updated to the latest generation
storage               4.13.0-0.nightly-2023-03-29-235439   True        True          False      20m     VSphereCSIDriverOperatorCRProgressing: Waiting for VSphere operator to report status
etcd                  4.13.0-0.nightly-2023-03-29-235439   True        True          True       22m     ClusterMemberControllerDegraded: unhealthy members found during reconciling members...
authentication        4.13.0-0.nightly-2023-03-29-235439   True        True          False      107s    APIServerDeploymentProgressing: deployment/apiserver.openshift-oauth-apiserver: 1/3 pods have been updated to the latest generation
kube-apiserver        4.13.0-0.nightly-2023-03-29-235439   True        True          False      21m     NodeInstallerProgressing: 3 nodes are at revision 6; 0 nodes have achieved new revision 7

The command should be failed because some operators are in a progressing state.