INFO: Log in to your Red Hat account... INFO: Configure AWS Credentials... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.59). WARN: It is recommended that you update to the latest version. INFO: Logged in as 'rhtap-shared' on 'https://api.openshift.com' INFO: Create ROSA with HCP cluster... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.59). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-4430e27743' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-4430e27743' has been created. INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information. Name: kx-4430e27743 Domain Prefix: kx-4430e27743 Display Name: kx-4430e27743 ID: 2nctddb2pnsj1kf5qaedtj4ss3f36js5 External ID: 5365b9ff-c86c-498a-9b74-22132cbfd27c Control Plane: ROSA Service Hosted OpenShift Version: 4.19.9 Channel Group: stable DNS: Not ready AWS Account: 381492310364 AWS Billing Account: 381492310364 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-0208a6297964e4fe1, subnet-0c161c939f7025e15, subnet-023e5c7b3016ed194, subnet-02dbd8abbf884d77f, subnet-0360c2d20442c5ba5, subnet-0aad9c992e402a91a EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cloud-network-config-controller-cloud-creden - arn:aws:iam::381492310364:role/rhads-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-control-plane-operator - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kms-provider - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kube-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-capa-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-openshift-ingress-operator-cloud-credentials Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Dec 24 2025 17:36:56 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/37Ik8sGUWvKuj09DAs3okL8ckLH OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2jtsga3i2etnl697l7bk5i1kmbm4a95j (Managed) Etcd Encryption: Disabled Audit Log Forwarding: Disabled External Authentication: Disabled Zero Egress: Disabled INFO: Preparing to create operator roles. INFO: Operator Roles already exists INFO: Preparing to create OIDC Provider. INFO: OIDC provider already exists INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-4430e27743'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-4430e27743 --watch'. INFO: Track the progress of the cluster creation... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.59). WARN: It is recommended that you update to the latest version. W: Region flag will be removed from this command in future versions INFO: Cluster 'kx-4430e27743' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-4430e27743 Version 2025-12-24 17:42:00 +0000 UTC hostedclusters kx-4430e27743 ValidAWSIdentityProvider StatusUnknown 2025-12-24 17:42:01 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-12-24 17:42:01 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Condition not found in the CVO. 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 HostedCluster is supported by operator configuration 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Release image is valid 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 Reconciliation active on resource 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:42:05 +0000 UTC hostedclusters kx-4430e27743 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-24 17:43:49 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-12-24 17:43:51 +0000 UTC hostedclusters kx-4430e27743 Configuration passes validation 2025-12-24 17:43:52 +0000 UTC hostedclusters kx-4430e27743 Required platform credentials are found 2025-12-24 17:43:54 +0000 UTC hostedclusters kx-4430e27743 AWS KMS is not configured 2025-12-24 17:43:54 +0000 UTC hostedclusters kx-4430e27743 capi-provider deployment has 1 unavailable replicas 2025-12-24 17:43:54 +0000 UTC hostedclusters kx-4430e27743 lookup api.kx-4430e27743.0yex.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-12-24 17:43:54 +0000 UTC hostedclusters kx-4430e27743 Configuration passes validation 2025-12-24 17:43:54 +0000 UTC hostedclusters kx-4430e27743 Waiting for etcd to reach quorum 2025-12-24 17:43:54 +0000 UTC hostedclusters kx-4430e27743 Kube APIServer deployment not found 2025-12-24 17:43:57 +0000 UTC hostedclusters kx-4430e27743 OIDC configuration is valid 2025-12-24 17:43:57 +0000 UTC hostedclusters kx-4430e27743 Reconciliation completed successfully 2025-12-24 17:44:01 +0000 UTC hostedclusters kx-4430e27743 All is well 2025-12-24 17:44:14 +0000 UTC hostedclusters kx-4430e27743 All is well 2025-12-24 17:44:24 +0000 UTC hostedclusters kx-4430e27743 WebIdentityErr 2025-12-24 17:44:41 +0000 UTC hostedclusters kx-4430e27743 EtcdAvailable QuorumAvailable 2025-12-24 17:45:23 +0000 UTC hostedclusters kx-4430e27743 Kube APIServer deployment is available 2025-12-24 17:45:45 +0000 UTC hostedclusters kx-4430e27743 Ignition server deployment is available 2025-12-24 17:45:53 +0000 UTC hostedclusters kx-4430e27743 ClusterVersionSucceeding FromClusterVersion 2025-12-24 17:45:53 +0000 UTC hostedclusters kx-4430e27743 Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-12-24 17:45:53 +0000 UTC hostedclusters kx-4430e27743 ClusterVersionAvailable FromClusterVersion 2025-12-24 17:45:53 +0000 UTC hostedclusters kx-4430e27743 Working towards 4.19.9: 283 of 629 done (44% complete) 2025-12-24 17:46:01 +0000 UTC hostedclusters kx-4430e27743 An update is already in progress and the details are in the Progressing condition 2025-12-24 17:46:24 +0000 UTC hostedclusters kx-4430e27743 Multiple errors are preventing progress: * Cluster operators dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, network, node-tuning, openshift-samples, service-ca are not available * Could not update imagestream "openshift/driver-toolkit" (447 of 629): resource may have been deleted * Could not update oauthclient "console" (378 of 629): the server does not recognize this resource, check extension API servers * Could not update operatorgroup "openshift-monitoring/openshift-cluster-monitoring" (570 of 629): resource may have been deleted * Could not update role "openshift-authentication/prometheus-k8s" (557 of 629): resource may have been deleted * Could not update role "openshift-console-operator/prometheus-k8s" (587 of 629): resource may have been deleted * Could not update role "openshift-console/prometheus-k8s" (591 of 629): resource may have been deleted * Could not update role "openshift-ingress-operator/prometheus-k8s" (598 of 629): resource may have been deleted * Could not update role "openshift-kube-apiserver-operator/prometheus-k8s" (602 of 629): resource may have been deleted 2025-12-24 17:46:24 +0000 UTC hostedclusters kx-4430e27743 All is well 2025-12-24 17:46:30 +0000 UTC hostedclusters kx-4430e27743 All is well 2025-12-24 17:46:39 +0000 UTC hostedclusters kx-4430e27743 Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-12-24 17:46:53 +0000 UTC hostedclusters kx-4430e27743 The hosted cluster is not degraded 2025-12-24 17:46:56 +0000 UTC hostedclusters kx-4430e27743 The hosted control plane is available INFO: Cluster 'kx-4430e27743' is now ready INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.59). WARN: It is recommended that you update to the latest version. INFO: Storing login command... INFO: Check if it's able to login to OCP cluster... Retried 1 times... INFO: Check if apiserver is ready... Waiting for cluster operators to be accessible for 2m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 3m50s dns 4.19.9 False False True 3m49s DNS "default" is unavailable. image-registry False True True 3m30s Available: The deployment does not have available replicas... ingress False True True 3m27s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 3m38s kube-controller-manager 4.19.9 True False False 3m38s kube-scheduler 4.19.9 True False False 3m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m22s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m26s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m38s openshift-controller-manager 4.19.9 True False False 3m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m40s operator-lifecycle-manager-catalog 4.19.9 True False False 3m41s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m37s service-ca storage 4.19.9 False False False 3m37s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service cluster operators to be accessible finished! [INFO] Cluster operators are accessible. Waiting for cluster to be reported as healthy for 60m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 3m50s dns 4.19.9 False False True 3m49s DNS "default" is unavailable. image-registry False True True 3m30s Available: The deployment does not have available replicas... ingress False True True 3m27s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 3m38s kube-controller-manager 4.19.9 True False False 3m38s kube-scheduler 4.19.9 True False False 3m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m22s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m26s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m38s openshift-controller-manager 4.19.9 True False False 3m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m40s operator-lifecycle-manager-catalog 4.19.9 True False False 3m41s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m37s service-ca storage 4.19.9 False False False 3m37s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 4m50s dns 4.19.9 False False True 4m49s DNS "default" is unavailable. image-registry False True True 4m30s Available: The deployment does not have available replicas... ingress False True True 4m27s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 4m38s kube-controller-manager 4.19.9 True False False 4m38s kube-scheduler 4.19.9 True False False 4m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m22s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m26s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m38s openshift-controller-manager 4.19.9 True False False 4m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m40s operator-lifecycle-manager-catalog 4.19.9 True False False 4m41s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m37s service-ca storage 4.19.9 False False False 4m37s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 5m50s dns 4.19.9 False False True 5m49s DNS "default" is unavailable. image-registry False True True 5m30s Available: The deployment does not have available replicas... ingress False True True 5m27s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 5m38s kube-controller-manager 4.19.9 True False False 5m38s kube-scheduler 4.19.9 True False False 5m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m22s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 5m26s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m38s openshift-controller-manager 4.19.9 True False False 5m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m40s operator-lifecycle-manager-catalog 4.19.9 True False False 5m41s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m37s service-ca storage 4.19.9 False False False 5m37s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 6m51s dns 4.19.9 False False True 6m50s DNS "default" is unavailable. image-registry False True True 6m31s Available: The deployment does not have available replicas... ingress False True True 6m28s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 6m39s kube-controller-manager 4.19.9 True False False 6m39s kube-scheduler 4.19.9 True False False 6m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m23s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 6m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 6m39s openshift-controller-manager 4.19.9 True False False 6m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m41s operator-lifecycle-manager-catalog 4.19.9 True False False 6m42s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m38s service-ca storage 4.19.9 False False False 6m38s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 7m51s dns 4.19.9 False False True 7m50s DNS "default" is unavailable. image-registry False True True 7m31s Available: The deployment does not have available replicas... ingress False True True 7m28s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 7m39s kube-controller-manager 4.19.9 True False False 7m39s kube-scheduler 4.19.9 True False False 7m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m23s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 7m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 7m39s openshift-controller-manager 4.19.9 True False False 7m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m41s operator-lifecycle-manager-catalog 4.19.9 True False False 7m42s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m38s service-ca storage 4.19.9 False False False 7m38s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 8m51s dns 4.19.9 False False True 8m50s DNS "default" is unavailable. image-registry False True True 8m31s Available: The deployment does not have available replicas... ingress False True True 8m28s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 8m39s kube-controller-manager 4.19.9 True False False 8m39s kube-scheduler 4.19.9 True False False 8m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m23s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 8m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 8m39s openshift-controller-manager 4.19.9 True False False 8m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m41s operator-lifecycle-manager-catalog 4.19.9 True False False 8m42s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m38s service-ca storage 4.19.9 False False False 8m38s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 9m51s dns 4.19.9 False False True 9m50s DNS "default" is unavailable. image-registry False True True 9m31s Available: The deployment does not have available replicas... ingress False True True 9m28s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 9m39s kube-controller-manager 4.19.9 True False False 9m39s kube-scheduler 4.19.9 True False False 9m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 9m23s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 2s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.19.9 True False False 9m39s openshift-controller-manager 4.19.9 True False False 9m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 9m41s operator-lifecycle-manager-catalog 4.19.9 True False False 9m42s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m38s service-ca storage 4.19.9 False True False 9m38s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 Unknown False False 2s csi-snapshot-controller 4.19.9 True False False 10m dns 4.19.9 False True True 10m DNS "default" is unavailable. image-registry False True True 10m Available: The deployment does not have available replicas... ingress False True True 10m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.19.9 True False False 27s kube-apiserver 4.19.9 True False False 10m kube-controller-manager 4.19.9 True False False 10m kube-scheduler 4.19.9 True False False 10m kube-storage-version-migrator 4.19.9 True False False 25s monitoring Unknown True Unknown 3s Rolling out the stack. network 4.19.9 True True False 10m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True False False 62s openshift-apiserver 4.19.9 True False False 10m openshift-controller-manager 4.19.9 True False False 10m openshift-samples operator-lifecycle-manager 4.19.9 True False False 10m operator-lifecycle-manager-catalog 4.19.9 True False False 10m operator-lifecycle-manager-packageserver 4.19.9 True False False 10m service-ca 4.19.9 True False False 25s storage 4.19.9 True False False 59s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 39s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 11m dns 4.19.9 True False False 44s image-registry True True False 9s Progressing: The deployment has not completed... ingress False True True 11m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.19.9 True False False 88s kube-apiserver 4.19.9 True False False 11m kube-controller-manager 4.19.9 True False False 11m kube-scheduler 4.19.9 True False False 11m kube-storage-version-migrator 4.19.9 True False False 86s monitoring Unknown True Unknown 64s Rolling out the stack. network 4.19.9 True False False 11m node-tuning 4.19.9 True False False 2m3s openshift-apiserver 4.19.9 True False False 11m openshift-controller-manager 4.19.9 True False False 11m openshift-samples 4.19.9 True False False 32s operator-lifecycle-manager 4.19.9 True False False 11m operator-lifecycle-manager-catalog 4.19.9 True False False 11m operator-lifecycle-manager-packageserver 4.19.9 True False False 11m service-ca 4.19.9 True False False 86s storage 4.19.9 True False False 2m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 99s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 12m dns 4.19.9 True False False 104s image-registry True True True 69s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-7bdf47f46" has timed out progressing. ingress 4.19.9 True True False 11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 2m28s kube-apiserver 4.19.9 True False False 12m kube-controller-manager 4.19.9 True False False 12m kube-scheduler 4.19.9 True False False 12m kube-storage-version-migrator 4.19.9 True False False 2m26s monitoring Unknown True Unknown 2m4s Rolling out the stack. network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 3m3s openshift-apiserver 4.19.9 True False False 12m openshift-controller-manager 4.19.9 True False False 12m openshift-samples 4.19.9 True False False 92s operator-lifecycle-manager 4.19.9 True False False 12m operator-lifecycle-manager-catalog 4.19.9 True False False 12m operator-lifecycle-manager-packageserver 4.19.9 True False False 12m service-ca 4.19.9 True False False 2m26s storage 4.19.9 True False False 3m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 2m39s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 13m dns 4.19.9 True False False 2m44s image-registry True True True 2m9s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-7bdf47f46" has timed out progressing. ingress 4.19.9 True True False 71s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 3m28s kube-apiserver 4.19.9 True False False 13m kube-controller-manager 4.19.9 True False False 13m kube-scheduler 4.19.9 True False False 13m kube-storage-version-migrator 4.19.9 True False False 3m26s monitoring Unknown True Unknown 3m4s Rolling out the stack. network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 4m3s openshift-apiserver 4.19.9 True False False 13m openshift-controller-manager 4.19.9 True False False 13m openshift-samples 4.19.9 True False False 2m32s operator-lifecycle-manager 4.19.9 True False False 13m operator-lifecycle-manager-catalog 4.19.9 True False False 13m operator-lifecycle-manager-packageserver 4.19.9 True False False 13m service-ca 4.19.9 True False False 3m26s storage 4.19.9 True False False 4m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 3m39s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 14m dns 4.19.9 True True False 3m44s DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2." image-registry True True True 3m9s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-7bdf47f46" has timed out progressing. ingress 4.19.9 True True False 2m11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 4m28s kube-apiserver 4.19.9 True False False 14m kube-controller-manager 4.19.9 True False False 14m kube-scheduler 4.19.9 True False False 14m kube-storage-version-migrator 4.19.9 True False False 4m26s monitoring Unknown True Unknown 4m4s Rolling out the stack. network 4.19.9 True True False 14m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 6s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.19.9 True False False 14m openshift-controller-manager 4.19.9 True False False 14m openshift-samples 4.19.9 True False False 3m32s operator-lifecycle-manager 4.19.9 True False False 14m operator-lifecycle-manager-catalog 4.19.9 True False False 14m operator-lifecycle-manager-packageserver 4.19.9 True False False 14m service-ca 4.19.9 True False False 4m26s storage 4.19.9 True True False 5m AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 4m40s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 15m dns 4.19.9 True False False 4m45s image-registry True True True 4m10s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-7bdf47f46" has timed out progressing. ingress 4.19.9 True True False 3m12s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 5m29s kube-apiserver 4.19.9 True False False 15m kube-controller-manager 4.19.9 True False False 15m kube-scheduler 4.19.9 True False False 15m kube-storage-version-migrator 4.19.9 True False False 5m27s monitoring Unknown True Unknown 5m5s Rolling out the stack. network 4.19.9 True True False 15m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.19.9 True False False 67s openshift-apiserver 4.19.9 True False False 15m openshift-controller-manager 4.19.9 True False False 15m openshift-samples 4.19.9 True False False 4m33s operator-lifecycle-manager 4.19.9 True False False 15m operator-lifecycle-manager-catalog 4.19.9 True False False 15m operator-lifecycle-manager-packageserver 4.19.9 True False False 15m service-ca 4.19.9 True False False 5m27s storage 4.19.9 True False False 6m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True False False 5m40s csi-snapshot-controller 4.19.9 True False False 16m dns 4.19.9 True False False 5m45s image-registry 4.19.9 True True False 5m10s Progressing: The deployment has not completed... ingress 4.19.9 True False False 4m12s insights 4.19.9 True False False 6m29s kube-apiserver 4.19.9 True False False 16m kube-controller-manager 4.19.9 True False False 16m kube-scheduler 4.19.9 True False False 16m kube-storage-version-migrator 4.19.9 True False False 6m27s monitoring Unknown True Unknown 6m5s Rolling out the stack. network 4.19.9 True False False 16m node-tuning 4.19.9 True False False 2m7s openshift-apiserver 4.19.9 True False False 16m openshift-controller-manager 4.19.9 True False False 16m openshift-samples 4.19.9 True False False 5m33s operator-lifecycle-manager 4.19.9 True False False 16m operator-lifecycle-manager-catalog 4.19.9 True False False 16m operator-lifecycle-manager-packageserver 4.19.9 True False False 16m service-ca 4.19.9 True False False 6m27s storage 4.19.9 True False False 7m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 6m41s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 17m dns 4.19.9 True False False 6m46s image-registry 4.19.9 True False False 6m11s ingress 4.19.9 True False False 5m13s insights 4.19.9 True False False 7m30s kube-apiserver 4.19.9 True False False 17m kube-controller-manager 4.19.9 True False False 17m kube-scheduler 4.19.9 True False False 17m kube-storage-version-migrator 4.19.9 True False False 7m28s monitoring 4.19.9 True False False 2s network 4.19.9 True False False 17m node-tuning 4.19.9 True False False 3m8s openshift-apiserver 4.19.9 True False False 17m openshift-controller-manager 4.19.9 True False False 17m openshift-samples 4.19.9 True False False 6m34s operator-lifecycle-manager 4.19.9 True False False 17m operator-lifecycle-manager-catalog 4.19.9 True False False 17m operator-lifecycle-manager-packageserver 4.19.9 True False False 17m service-ca 4.19.9 True False False 7m28s storage 4.19.9 True False False 8m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True False False 7m41s csi-snapshot-controller 4.19.9 True False False 18m dns 4.19.9 True False False 7m46s image-registry 4.19.9 True False False 7m11s ingress 4.19.9 True False False 6m13s insights 4.19.9 True False False 8m30s kube-apiserver 4.19.9 True False False 18m kube-controller-manager 4.19.9 True False False 18m kube-scheduler 4.19.9 True False False 18m kube-storage-version-migrator 4.19.9 True False False 8m28s monitoring 4.19.9 True False False 62s network 4.19.9 True False False 18m node-tuning 4.19.9 True False False 4m8s openshift-apiserver 4.19.9 True False False 18m openshift-controller-manager 4.19.9 True False False 18m openshift-samples 4.19.9 True False False 7m34s operator-lifecycle-manager 4.19.9 True False False 18m operator-lifecycle-manager-catalog 4.19.9 True False False 18m operator-lifecycle-manager-packageserver 4.19.9 True False False 18m service-ca 4.19.9 True False False 8m28s storage 4.19.9 True False False 9m2s Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!