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-bc4c31a258' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-bc4c31a258' 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-bc4c31a258 Domain Prefix: kx-bc4c31a258 Display Name: kx-bc4c31a258 ID: 2nbu3r757pls45broknnkgsjdg7caksb External ID: 6b3694f6-4c91-4e5b-9cdf-36972af3d88f 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-ingress-operator-cloud-credentials - 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-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 Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Dec 23 2025 06:00:16 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/37EYIJFOREn9bHirydm9qaOGQkC 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-bc4c31a258'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-bc4c31a258 --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-bc4c31a258' 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-bc4c31a258 Version 2025-12-23 06:06:12 +0000 UTC hostedclusters kx-bc4c31a258 ValidAWSIdentityProvider StatusUnknown 2025-12-23 06:06:13 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-12-23 06:06:13 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Ignition server deployment not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 HostedCluster is supported by operator configuration 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Release image is valid 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Reconciliation active on resource 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is not found 2025-12-23 06:06:19 +0000 UTC hostedclusters kx-bc4c31a258 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-23 06:06:19 +0000 UTC hostedclusters kx-bc4c31a258 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-bc4c31a258 Version 2025-12-23 06:06:12 +0000 UTC hostedclusters kx-bc4c31a258 ValidAWSIdentityProvider StatusUnknown 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Release image is valid 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Ignition server deployment not found 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Reconciliation active on resource 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 HostedCluster is supported by operator configuration 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Waiting for hosted control plane kubeconfig to be created 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Condition not found in the CVO. 2025-12-23 06:06:19 +0000 UTC hostedclusters kx-bc4c31a258 HostedCluster is at expected version 2025-12-23 06:07:40 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-12-23 06:07:43 +0000 UTC hostedclusters kx-bc4c31a258 Configuration passes validation 2025-12-23 06:07:44 +0000 UTC hostedclusters kx-bc4c31a258 Required platform credentials are found 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 Configuration passes validation 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 capi-provider deployment has 1 unavailable replicas 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 AWS KMS is not configured 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 Waiting for etcd to reach quorum 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 Kube APIServer deployment not found 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 lookup api.kx-bc4c31a258.7zyr.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-12-23 06:07:51 +0000 UTC hostedclusters kx-bc4c31a258 OIDC configuration is valid 2025-12-23 06:07:51 +0000 UTC hostedclusters kx-bc4c31a258 Reconciliation completed successfully 2025-12-23 06:08:07 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:08:07 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:08:07 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:08:07 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:08:16 +0000 UTC hostedclusters kx-bc4c31a258 WebIdentityErr 2025-12-23 06:08:34 +0000 UTC hostedclusters kx-bc4c31a258 EtcdAvailable QuorumAvailable 2025-12-23 06:09:07 +0000 UTC hostedclusters kx-bc4c31a258 Kube APIServer deployment is available 2025-12-23 06:09:16 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:09:27 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:09:31 +0000 UTC hostedclusters kx-bc4c31a258 Ignition server deployment is available 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 ClusterVersionSucceeding FromClusterVersion 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 ClusterVersionAvailable FromClusterVersion 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 Working towards 4.19.9: 285 of 629 done (45% complete) 2025-12-23 06:09:47 +0000 UTC hostedclusters kx-bc4c31a258 An update is already in progress and the details are in the Progressing condition 2025-12-23 06:10:10 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is available 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-bc4c31a258 Version 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Reconciliation active on resource 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 Release image is valid 2025-12-23 06:06:18 +0000 UTC hostedclusters kx-bc4c31a258 HostedCluster is supported by operator configuration 2025-12-23 06:06:19 +0000 UTC hostedclusters kx-bc4c31a258 HostedCluster is at expected version 2025-12-23 06:07:40 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-12-23 06:07:43 +0000 UTC hostedclusters kx-bc4c31a258 Configuration passes validation 2025-12-23 06:07:44 +0000 UTC hostedclusters kx-bc4c31a258 Required platform credentials are found 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 Configuration passes validation 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 AWS KMS is not configured 2025-12-23 06:07:47 +0000 UTC hostedclusters kx-bc4c31a258 lookup api.kx-bc4c31a258.7zyr.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-12-23 06:07:51 +0000 UTC hostedclusters kx-bc4c31a258 Reconciliation completed successfully 2025-12-23 06:07:51 +0000 UTC hostedclusters kx-bc4c31a258 OIDC configuration is valid 2025-12-23 06:08:07 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:08:07 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:08:34 +0000 UTC hostedclusters kx-bc4c31a258 EtcdAvailable QuorumAvailable 2025-12-23 06:09:07 +0000 UTC hostedclusters kx-bc4c31a258 Kube APIServer deployment is available 2025-12-23 06:09:16 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:09:27 +0000 UTC hostedclusters kx-bc4c31a258 All is well 2025-12-23 06:09:31 +0000 UTC hostedclusters kx-bc4c31a258 Ignition server deployment is available 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 ClusterVersionAvailable FromClusterVersion 2025-12-23 06:09:41 +0000 UTC hostedclusters kx-bc4c31a258 Unable to apply 4.19.9: some cluster operators are not available 2025-12-23 06:09:47 +0000 UTC hostedclusters kx-bc4c31a258 An update is already in progress and the details are in the Progressing condition 2025-12-23 06:10:11 +0000 UTC hostedclusters kx-bc4c31a258 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-23 06:10:31 +0000 UTC hostedclusters kx-bc4c31a258 The hosted cluster is not degraded 2025-12-23 06:10:33 +0000 UTC hostedclusters kx-bc4c31a258 The hosted control plane is available INFO: Cluster 'kx-bc4c31a258' 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 4m20s dns 4.19.9 False False True 4m18s DNS "default" is unavailable. image-registry False True True 4m2s Available: The deployment does not have available replicas... ingress False True True 4m 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 4m6s kube-controller-manager 4.19.9 True False False 4m6s kube-scheduler 4.19.9 True False False 4m6s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m52s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m7s openshift-controller-manager 4.19.9 True False False 4m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m8s operator-lifecycle-manager-catalog 4.19.9 True False False 4m1s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m6s service-ca storage 4.19.9 False False False 4m6s 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 4m20s dns 4.19.9 False False True 4m18s DNS "default" is unavailable. image-registry False True True 4m2s Available: The deployment does not have available replicas... ingress False True True 4m 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 4m6s kube-controller-manager 4.19.9 True False False 4m6s kube-scheduler 4.19.9 True False False 4m6s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m52s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m7s openshift-controller-manager 4.19.9 True False False 4m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m8s operator-lifecycle-manager-catalog 4.19.9 True False False 4m1s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m6s service-ca storage 4.19.9 False False False 4m6s 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 5m20s dns 4.19.9 False False True 5m18s DNS "default" is unavailable. image-registry False True True 5m2s Available: The deployment does not have available replicas... ingress False True True 5m 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 5m6s kube-controller-manager 4.19.9 True False False 5m6s kube-scheduler 4.19.9 True False False 5m6s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m52s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m7s openshift-controller-manager 4.19.9 True False False 5m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m8s operator-lifecycle-manager-catalog 4.19.9 True False False 5m1s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m6s service-ca storage 4.19.9 False False False 5m6s 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 6m20s dns 4.19.9 False False True 6m18s DNS "default" is unavailable. image-registry False True True 6m2s Available: The deployment does not have available replicas... ingress False True True 6m 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 6m6s kube-controller-manager 4.19.9 True False False 6m6s kube-scheduler 4.19.9 True False False 6m6s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m52s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 5m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 6m7s openshift-controller-manager 4.19.9 True False False 6m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m8s operator-lifecycle-manager-catalog 4.19.9 True False False 6m1s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m6s service-ca storage 4.19.9 False False False 6m6s 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 7m21s dns 4.19.9 False False True 7m19s DNS "default" is unavailable. image-registry False True True 7m3s Available: The deployment does not have available replicas... ingress False True True 7m1s 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 7m7s kube-controller-manager 4.19.9 True False False 7m7s kube-scheduler 4.19.9 True False False 7m7s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m53s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 6m38s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 7m8s openshift-controller-manager 4.19.9 True False False 7m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m9s operator-lifecycle-manager-catalog 4.19.9 True False False 7m2s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m7s service-ca storage 4.19.9 False False False 7m7s 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 8m21s dns 4.19.9 False False True 8m19s DNS "default" is unavailable. image-registry False True True 8m3s Available: The deployment does not have available replicas... ingress False True True 8m1s 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 8m7s kube-controller-manager 4.19.9 True False False 8m7s kube-scheduler 4.19.9 True False False 8m7s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m53s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 7m38s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 8m8s openshift-controller-manager 4.19.9 True False False 8m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m9s operator-lifecycle-manager-catalog 4.19.9 True False False 8m2s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m7s service-ca storage 4.19.9 False False False 8m7s 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 9m21s dns 4.19.9 False False True 9m19s DNS "default" is unavailable. image-registry False True True 9m3s Available: The deployment does not have available replicas... ingress False True True 9m1s 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 9m7s kube-controller-manager 4.19.9 True False False 9m7s kube-scheduler 4.19.9 True False False 9m7s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m53s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 3 nodes)... node-tuning 4.19.9 True True False 17s Waiting for 3/3 Profiles to be applied openshift-apiserver 4.19.9 True False False 9m8s openshift-controller-manager 4.19.9 True False False 9m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 9m9s operator-lifecycle-manager-catalog 4.19.9 True False False 9m2s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m7s service-ca storage 4.19.9 True False False 7s 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 10s 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 30s 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 26s monitoring Unknown True Unknown 0s Rolling out the stack. network 4.19.9 True True False 9m53s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes) node-tuning 4.19.9 True False False 77s 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 27s storage 4.19.9 True False False 67s 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 49s csi-snapshot-controller 4.19.9 True False False 11m dns 4.19.9 True False False 55s image-registry 4.19.9 True False False 56s ingress 4.19.9 True False True 32s The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller). insights 4.19.9 True False False 90s 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 60s Rolling out the stack. network 4.19.9 True False False 10m node-tuning 4.19.9 True False False 2m17s 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 44s 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 87s storage 4.19.9 True False False 2m7s 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 110s 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 116s image-registry 4.19.9 True False False 117s ingress 4.19.9 True False True 93s The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller). insights 4.19.9 True False False 2m31s 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 2m27s monitoring Unknown True Unknown 2m1s Rolling out the stack. network 4.19.9 True False False 11m node-tuning 4.19.9 True False False 3m18s 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 105s 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 2m28s storage 4.19.9 True False False 3m8s 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 2m50s csi-snapshot-controller 4.19.9 True False False 13m dns 4.19.9 True False False 2m56s image-registry 4.19.9 True False False 2m57s ingress 4.19.9 True False False 2m33s insights 4.19.9 True False False 3m31s 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 3m27s monitoring Unknown True Unknown 3m1s Rolling out the stack. network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 4m18s 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 2m45s 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 3m28s storage 4.19.9 True False False 4m8s 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 3m50s csi-snapshot-controller 4.19.9 True False False 14m dns 4.19.9 True False False 3m56s image-registry 4.19.9 True False False 3m57s ingress 4.19.9 True False False 3m33s insights 4.19.9 True False False 4m31s 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 4m27s monitoring Unknown True Unknown 4m1s Rolling out the stack. network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 5m18s 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 3m45s 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 4m28s storage 4.19.9 True False False 5m8s 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 4m51s csi-snapshot-controller 4.19.9 True False False 15m dns 4.19.9 True False False 4m57s image-registry 4.19.9 True False False 4m58s ingress 4.19.9 True False False 4m34s insights 4.19.9 True False False 5m32s 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 5m28s monitoring 4.19.9 True False False 11s network 4.19.9 True False False 14m node-tuning 4.19.9 True False False 6m19s 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 4m46s 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 5m29s storage 4.19.9 True False False 6m9s Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!