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.57). 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.57). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-51cf0a37de' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-51cf0a37de' 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-51cf0a37de Domain Prefix: kx-51cf0a37de Display Name: kx-51cf0a37de ID: 2m8hi9pa9l684elbfeeafbab8eoapm11 External ID: 25ab9f35-3eb6-4bba-b6a2-66baeb49b9b8 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-cloud-network-config-controller-cloud-creden - 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-kube-system-control-plane-operator - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kms-provider - arn:aws:iam::381492310364:role/rhads-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 30 2025 13:25:06 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34mtj2gg3vOuHqw1NpYeUCfTm6s 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-51cf0a37de'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-51cf0a37de --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.57). 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-51cf0a37de' 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-51cf0a37de Version 2025-10-30 13:29:10 +0000 UTC hostedclusters kx-51cf0a37de ValidAWSIdentityProvider StatusUnknown 2025-10-30 13:29:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-30 13:29:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Ignition server deployment not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is supported by operator configuration 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Release image is valid 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation active on resource 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is not found 2025-10-30 13:29:14 +0000 UTC hostedclusters kx-51cf0a37de configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-51cf0a37de Version 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Release image is valid 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Waiting for hosted control plane kubeconfig to be created 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation active on resource 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is at expected version 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Ignition server deployment not found 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is supported by operator configuration 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Condition not found in the CVO. 2025-10-30 14:16:44 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-30 14:16:52 +0000 UTC hostedclusters kx-51cf0a37de Configuration passes validation 2025-10-30 14:16:53 +0000 UTC hostedclusters kx-51cf0a37de Required platform credentials are found 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de AWS KMS is not configured 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de capi-provider deployment has 2 unavailable replicas 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de lookup api.kx-51cf0a37de.tnfg.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de Configuration passes validation 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de Waiting for etcd to reach quorum 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de Kube APIServer deployment not found 2025-10-30 14:16:59 +0000 UTC hostedclusters kx-51cf0a37de OIDC configuration is valid 2025-10-30 14:16:59 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation completed successfully 2025-10-30 14:17:19 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:17:19 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:17:25 +0000 UTC hostedclusters kx-51cf0a37de WebIdentityErr 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-51cf0a37de Version 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is at expected version 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation active on resource 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Get "https://a4e6ec869d6b04afba121e266269dc22-84e5c94a82b3cc09.elb.us-east-1.amazonaws.com:443/healthz": dial tcp: lookup a4e6ec869d6b04afba121e266269dc22-84e5c94a82b3cc09.elb.us-east-1.amazonaws.com on 172.30.0.10:53: no such host 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Release image is valid 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is supported by operator configuration 2025-10-30 14:16:44 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-30 14:16:52 +0000 UTC hostedclusters kx-51cf0a37de Configuration passes validation 2025-10-30 14:16:53 +0000 UTC hostedclusters kx-51cf0a37de Required platform credentials are found 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de Configuration passes validation 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de [capi-provider deployment has 1 unavailable replicas, router deployment has 1 unavailable replicas] 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de AWS KMS is not configured 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de lookup api.kx-51cf0a37de.tnfg.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-30 14:16:59 +0000 UTC hostedclusters kx-51cf0a37de OIDC configuration is valid 2025-10-30 14:16:59 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation completed successfully 2025-10-30 14:17:19 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:17:19 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:17:52 +0000 UTC hostedclusters kx-51cf0a37de EtcdAvailable QuorumAvailable 2025-10-30 14:18:26 +0000 UTC hostedclusters kx-51cf0a37de Kube APIServer deployment is available 2025-10-30 14:18:50 +0000 UTC hostedclusters kx-51cf0a37de Ignition server deployment is available 2025-10-30 14:18:55 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:18:57 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:19:18 +0000 UTC hostedclusters kx-51cf0a37de Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-30 14:19:18 +0000 UTC hostedclusters kx-51cf0a37de ClusterVersionAvailable FromClusterVersion 2025-10-30 14:19:18 +0000 UTC hostedclusters kx-51cf0a37de Unable to apply 4.19.9: some cluster operators are not available 2025-10-30 14:19:25 +0000 UTC hostedclusters kx-51cf0a37de An update is already in progress and the details are in the Progressing condition 2025-10-30 14:19:48 +0000 UTC hostedclusters kx-51cf0a37de Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, network, node-tuning, openshift-samples, service-ca, storage are not available 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-51cf0a37de Version 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is at expected version 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation active on resource 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de Release image is valid 2025-10-30 13:29:13 +0000 UTC hostedclusters kx-51cf0a37de HostedCluster is supported by operator configuration 2025-10-30 14:16:44 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-30 14:16:52 +0000 UTC hostedclusters kx-51cf0a37de Configuration passes validation 2025-10-30 14:16:53 +0000 UTC hostedclusters kx-51cf0a37de Required platform credentials are found 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de Configuration passes validation 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de lookup api.kx-51cf0a37de.tnfg.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-30 14:16:56 +0000 UTC hostedclusters kx-51cf0a37de AWS KMS is not configured 2025-10-30 14:16:59 +0000 UTC hostedclusters kx-51cf0a37de Reconciliation completed successfully 2025-10-30 14:16:59 +0000 UTC hostedclusters kx-51cf0a37de OIDC configuration is valid 2025-10-30 14:17:19 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:17:19 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:17:52 +0000 UTC hostedclusters kx-51cf0a37de EtcdAvailable QuorumAvailable 2025-10-30 14:18:26 +0000 UTC hostedclusters kx-51cf0a37de Kube APIServer deployment is available 2025-10-30 14:18:50 +0000 UTC hostedclusters kx-51cf0a37de Ignition server deployment is available 2025-10-30 14:18:55 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:18:57 +0000 UTC hostedclusters kx-51cf0a37de All is well 2025-10-30 14:19:18 +0000 UTC hostedclusters kx-51cf0a37de Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-30 14:19:18 +0000 UTC hostedclusters kx-51cf0a37de ClusterVersionAvailable FromClusterVersion 2025-10-30 14:19:18 +0000 UTC hostedclusters kx-51cf0a37de Unable to apply 4.19.9: some cluster operators are not available 2025-10-30 14:19:25 +0000 UTC hostedclusters kx-51cf0a37de An update is already in progress and the details are in the Progressing condition 2025-10-30 14:19:48 +0000 UTC hostedclusters kx-51cf0a37de Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-10-30 14:20:12 +0000 UTC hostedclusters kx-51cf0a37de The hosted cluster is not degraded 2025-10-30 14:20:18 +0000 UTC hostedclusters kx-51cf0a37de The hosted control plane is available INFO: Cluster 'kx-51cf0a37de' 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.57). 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 4m28s dns 4.19.9 False False True 4m30s DNS "default" is unavailable. image-registry False True True 4m17s Available: The deployment does not have available replicas... ingress False True True 4m10s 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 4m20s kube-controller-manager 4.19.9 True False False 4m20s kube-scheduler 4.19.9 True False False 4m20s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m52s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m5s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m20s openshift-controller-manager 4.19.9 True False False 4m20s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m22s operator-lifecycle-manager-catalog 4.19.9 True False False 4m14s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m20s service-ca storage 4.19.9 False False False 4m20s 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 4m28s dns 4.19.9 False False True 4m30s DNS "default" is unavailable. image-registry False True True 4m17s Available: The deployment does not have available replicas... ingress False True True 4m10s 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 4m20s kube-controller-manager 4.19.9 True False False 4m20s kube-scheduler 4.19.9 True False False 4m20s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m52s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m5s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m20s openshift-controller-manager 4.19.9 True False False 4m20s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m22s operator-lifecycle-manager-catalog 4.19.9 True False False 4m14s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m20s service-ca storage 4.19.9 False False False 4m20s 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 5m29s dns 4.19.9 False False True 5m31s DNS "default" is unavailable. image-registry False True True 5m18s Available: The deployment does not have available replicas... ingress False True True 5m11s 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 5m21s kube-controller-manager 4.19.9 True False False 5m21s kube-scheduler 4.19.9 True False False 5m21s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m53s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 5m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m21s openshift-controller-manager 4.19.9 True False False 5m21s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m23s operator-lifecycle-manager-catalog 4.19.9 True False False 5m15s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m21s service-ca storage 4.19.9 False False False 5m21s 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 6m29s dns 4.19.9 False False True 6m31s DNS "default" is unavailable. image-registry False True True 6m18s Available: The deployment does not have available replicas... ingress False True True 6m11s 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 6m21s kube-controller-manager 4.19.9 True False False 6m21s kube-scheduler 4.19.9 True False False 6m21s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m53s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 6m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 6m21s openshift-controller-manager 4.19.9 True False False 6m21s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m23s operator-lifecycle-manager-catalog 4.19.9 True False False 6m15s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m21s service-ca storage 4.19.9 False False False 6m21s 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 7m29s dns 4.19.9 False False True 7m31s DNS "default" is unavailable. image-registry False True True 7m18s Available: The deployment does not have available replicas... ingress False True True 7m11s 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 7m21s kube-controller-manager 4.19.9 True False False 7m21s kube-scheduler 4.19.9 True False False 7m21s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m53s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 7m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 7m21s openshift-controller-manager 4.19.9 True False False 7m21s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m23s operator-lifecycle-manager-catalog 4.19.9 True False False 7m15s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m21s service-ca storage 4.19.9 False False False 7m21s 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 8m29s dns 4.19.9 False False True 8m31s DNS "default" is unavailable. image-registry False True True 8m18s Available: The deployment does not have available replicas... ingress False True True 8m11s 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 8m21s kube-controller-manager 4.19.9 True False False 8m21s kube-scheduler 4.19.9 True False False 8m21s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m53s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 8m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 8m21s openshift-controller-manager 4.19.9 True False False 8m21s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m23s operator-lifecycle-manager-catalog 4.19.9 True False False 8m15s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m21s service-ca storage 4.19.9 False False False 8m21s 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 9m29s dns 4.19.9 False False True 9m31s DNS "default" is unavailable. image-registry False True True 9m18s Available: The deployment does not have available replicas... ingress False True True 9m11s 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 9m21s kube-controller-manager 4.19.9 True False False 9m21s kube-scheduler 4.19.9 True False False 9m21s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m53s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 9m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 9m21s openshift-controller-manager 4.19.9 True False False 9m21s openshift-samples operator-lifecycle-manager 4.19.9 True False False 9m23s operator-lifecycle-manager-catalog 4.19.9 True False False 9m15s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m21s service-ca storage 4.19.9 False False False 9m21s 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 10m dns 4.19.9 False False 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 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 monitoring network 4.19.9 True True False 9m54s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.19.9 True True False 33s Waiting for 1/1 Profiles to be applied 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 storage 4.19.9 True False False 30s 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 5s 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 28s image-registry True True False 13s Progressing: The deployment has not completed... ingress 4.19.9 True True False 2s 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 58s 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 55s monitoring Unknown True Unknown 31s Rolling out the stack. network 4.19.9 True True False 10m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready node-tuning 4.19.9 True False False 93s 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 16s 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 56s storage 4.19.9 True False False 90s 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 65s 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 88s image-registry True True True 73s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-599c56cbdf" has timed out progressing. ingress 4.19.9 True True False 62s 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 118s 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 115s monitoring Unknown True Unknown 91s Rolling out the stack. network 4.19.9 True False False 11m node-tuning 4.19.9 True False False 2m33s 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 76s 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 116s storage 4.19.9 True False False 2m30s 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 2m5s 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 2m28s image-registry True True True 2m13s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-599c56cbdf" has timed out progressing. ingress 4.19.9 True True False 2m2s 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 2m58s 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 2m55s monitoring Unknown True Unknown 2m31s Rolling out the stack. network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 3m33s 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 2m16s 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 2m56s storage 4.19.9 True False False 3m30s 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 3m6s 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 False False 3m29s image-registry True True True 3m14s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-599c56cbdf" has timed out progressing. ingress 4.19.9 True True False 3m3s 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 3m59s 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 3m56s monitoring Unknown True Unknown 3m32s Rolling out the stack. network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 4m34s 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 3m17s 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 3m57s storage 4.19.9 True False False 4m31s 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 4m6s 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 True False 4m29s DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2." image-registry True True True 4m14s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-599c56cbdf" has timed out progressing. ingress 4.19.9 True True False 4m3s 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 4m59s 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 4m56s monitoring Unknown True Unknown 4m32s 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 30s Waiting for 1/2 Profiles to be applied 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 4m17s 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 4m57s storage 4.19.9 True True False 5m31s 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 5m6s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 16m dns 4.19.9 True False False 5m29s image-registry True True True 5m14s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-599c56cbdf" has timed out progressing. ingress 4.19.9 True True False 5m3s 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 5m59s 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 5m56s monitoring Unknown True Unknown 5m32s 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 90s 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 5m17s 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 5m57s storage 4.19.9 True False False 6m31s 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 6m6s csi-snapshot-controller 4.19.9 True False False 17m dns 4.19.9 True False False 6m29s image-registry 4.19.9 True True False 6m14s Progressing: The deployment has not completed... ingress 4.19.9 True False False 6m3s insights 4.19.9 True False False 6m59s 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 6m56s monitoring Unknown True Unknown 6m32s Rolling out the stack. network 4.19.9 True False False 16m node-tuning 4.19.9 True False False 2m30s 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 6m17s 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 6m57s storage 4.19.9 True False False 7m31s 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 7m7s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 18m dns 4.19.9 True False False 7m30s image-registry 4.19.9 True False False 7m15s ingress 4.19.9 True False False 7m4s insights 4.19.9 True False False 8m 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 7m57s monitoring 4.19.9 True False False 7s network 4.19.9 True False False 17m node-tuning 4.19.9 True False False 3m31s 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 7m18s 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 7m58s storage 4.19.9 True False False 8m32s 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 8m7s csi-snapshot-controller 4.19.9 True False False 19m dns 4.19.9 True False False 8m30s image-registry 4.19.9 True False False 8m15s ingress 4.19.9 True False False 8m4s insights 4.19.9 True False False 9m kube-apiserver 4.19.9 True False False 19m kube-controller-manager 4.19.9 True False False 19m kube-scheduler 4.19.9 True False False 19m kube-storage-version-migrator 4.19.9 True False False 8m57s monitoring 4.19.9 True False False 67s network 4.19.9 True False False 18m node-tuning 4.19.9 True False False 4m31s openshift-apiserver 4.19.9 True False False 19m openshift-controller-manager 4.19.9 True False False 19m openshift-samples 4.19.9 True False False 8m18s operator-lifecycle-manager 4.19.9 True False False 19m operator-lifecycle-manager-catalog 4.19.9 True False False 19m operator-lifecycle-manager-packageserver 4.19.9 True False False 19m service-ca 4.19.9 True False False 8m58s storage 4.19.9 True False False 9m32s 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 9m7s csi-snapshot-controller 4.19.9 True False False 20m dns 4.19.9 True True False 9m30s DNS "default" reports Progressing=True: "Have 2 available node-resolver pods, want 3." image-registry 4.19.9 True True False 9m15s Progressing: The registry is ready... ingress 4.19.9 True False False 9m4s insights 4.19.9 True False False 10m kube-apiserver 4.19.9 True False False 20m kube-controller-manager 4.19.9 True False False 20m kube-scheduler 4.19.9 True False False 20m kube-storage-version-migrator 4.19.9 True False False 9m57s monitoring 4.19.9 True False False 2m7s network 4.19.9 True True False 19m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 45s Waiting for 1/3 Profiles to be applied openshift-apiserver 4.19.9 True False False 20m openshift-controller-manager 4.19.9 True False False 20m openshift-samples 4.19.9 True False False 9m18s operator-lifecycle-manager 4.19.9 True False False 20m operator-lifecycle-manager-catalog 4.19.9 True False False 20m operator-lifecycle-manager-packageserver 4.19.9 True False False 20m service-ca 4.19.9 True False False 9m58s storage 4.19.9 True True False 10m AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!