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-3b18058cbc' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-3b18058cbc' 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-3b18058cbc Domain Prefix: kx-3b18058cbc Display Name: kx-3b18058cbc ID: 2m3u18qat5dl9drgsq17lqk6hv9m9eas External ID: 8608efb1-6e6c-4d11-b32a-c6e3c5a04ce9 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-openshift-image-registry-installer-cloud-credentials - 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 Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 23 2025 13:33:34 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34T8tFHyJlxiUUz2mbKgeF0R8xf 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-3b18058cbc'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-3b18058cbc --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-3b18058cbc' 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-3b18058cbc Version 2025-10-23 13:37:54 +0000 UTC hostedclusters kx-3b18058cbc ValidAWSIdentityProvider StatusUnknown 2025-10-23 13:37:55 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-23 13:37:55 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Ignition server deployment not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc HostedCluster is supported by operator configuration 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Release image is valid 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Reconciliation active on resource 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:58 +0000 UTC hostedclusters kx-3b18058cbc configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-23 13:37:58 +0000 UTC hostedclusters kx-3b18058cbc 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-3b18058cbc Version 2025-10-23 13:37:54 +0000 UTC hostedclusters kx-3b18058cbc ValidAWSIdentityProvider StatusUnknown 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the HCP 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the HCP 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the HCP 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the HCP 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the HCP 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Ignition server deployment not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the HCP 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Waiting for hosted control plane to be healthy 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Condition not found in the CVO. 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Reconciliation active on resource 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc HostedCluster is supported by operator configuration 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is not found 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Release image is valid 2025-10-23 13:37:58 +0000 UTC hostedclusters kx-3b18058cbc HostedCluster is at expected version 2025-10-23 13:39:23 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-23 13:39:28 +0000 UTC hostedclusters kx-3b18058cbc Configuration passes validation 2025-10-23 13:39:30 +0000 UTC hostedclusters kx-3b18058cbc Required platform credentials are found 2025-10-23 13:39:37 +0000 UTC hostedclusters kx-3b18058cbc OIDC configuration is valid 2025-10-23 13:39:37 +0000 UTC hostedclusters kx-3b18058cbc Reconciliation completed successfully 2025-10-23 13:39:57 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:39:57 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:40:02 +0000 UTC hostedclusters kx-3b18058cbc WebIdentityErr 2025-10-23 13:40:15 +0000 UTC hostedclusters kx-3b18058cbc EtcdAvailable QuorumAvailable 2025-10-23 13:41:16 +0000 UTC hostedclusters kx-3b18058cbc Kube APIServer deployment is available 2025-10-23 13:41:32 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc ClusterVersionAvailable FromClusterVersion 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc Unable to apply 4.19.9: an unknown error has occurred: MultipleErrors 2025-10-23 13:41:56 +0000 UTC hostedclusters kx-3b18058cbc Ignition server deployment is available 2025-10-23 13:42:00 +0000 UTC hostedclusters kx-3b18058cbc An update is already in progress and the details are in the Progressing condition 2025-10-23 13:42:22 +0000 UTC hostedclusters kx-3b18058cbc Multiple errors are preventing progress: * Cluster operators console, 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 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 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-3b18058cbc Version 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Reconciliation active on resource 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc Release image is valid 2025-10-23 13:37:57 +0000 UTC hostedclusters kx-3b18058cbc HostedCluster is supported by operator configuration 2025-10-23 13:37:58 +0000 UTC hostedclusters kx-3b18058cbc HostedCluster is at expected version 2025-10-23 13:39:23 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-23 13:39:28 +0000 UTC hostedclusters kx-3b18058cbc Configuration passes validation 2025-10-23 13:39:30 +0000 UTC hostedclusters kx-3b18058cbc Required platform credentials are found 2025-10-23 13:39:33 +0000 UTC hostedclusters kx-3b18058cbc Configuration passes validation 2025-10-23 13:39:33 +0000 UTC hostedclusters kx-3b18058cbc AWS KMS is not configured 2025-10-23 13:39:33 +0000 UTC hostedclusters kx-3b18058cbc lookup api.kx-3b18058cbc.apam.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-23 13:39:37 +0000 UTC hostedclusters kx-3b18058cbc Reconciliation completed successfully 2025-10-23 13:39:37 +0000 UTC hostedclusters kx-3b18058cbc OIDC configuration is valid 2025-10-23 13:39:57 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:39:57 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:40:15 +0000 UTC hostedclusters kx-3b18058cbc EtcdAvailable QuorumAvailable 2025-10-23 13:41:16 +0000 UTC hostedclusters kx-3b18058cbc Kube APIServer deployment is available 2025-10-23 13:41:32 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc All is well 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc ClusterVersionAvailable FromClusterVersion 2025-10-23 13:41:53 +0000 UTC hostedclusters kx-3b18058cbc Unable to apply 4.19.9: some cluster operators are not available 2025-10-23 13:41:56 +0000 UTC hostedclusters kx-3b18058cbc Ignition server deployment is available 2025-10-23 13:42:00 +0000 UTC hostedclusters kx-3b18058cbc An update is already in progress and the details are in the Progressing condition 2025-10-23 13:42:22 +0000 UTC hostedclusters kx-3b18058cbc 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-23 13:42:59 +0000 UTC hostedclusters kx-3b18058cbc The hosted cluster is not degraded 2025-10-23 13:43:10 +0000 UTC hostedclusters kx-3b18058cbc The hosted control plane is available INFO: Cluster 'kx-3b18058cbc' 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 3m47s dns 4.19.9 False False True 3m44s DNS "default" is unavailable. image-registry False True True 2m56s Available: The deployment does not have available replicas... ingress False True True 3m28s 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 3m35s kube-controller-manager 4.19.9 True False False 3m35s kube-scheduler 4.19.9 True False False 3m35s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m19s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m38s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m35s openshift-controller-manager 4.19.9 True False False 3m35s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m38s operator-lifecycle-manager-catalog 4.19.9 True False False 3m30s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m35s service-ca storage 4.19.9 False False False 3m34s 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 3m48s dns 4.19.9 False False True 3m45s DNS "default" is unavailable. image-registry False True True 2m57s Available: The deployment does not have available replicas... ingress False True True 3m29s 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 3m36s kube-controller-manager 4.19.9 True False False 3m36s kube-scheduler 4.19.9 True False False 3m36s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m20s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m39s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m36s openshift-controller-manager 4.19.9 True False False 3m36s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m39s operator-lifecycle-manager-catalog 4.19.9 True False False 3m31s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m36s service-ca storage 4.19.9 False False False 3m35s 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 4m48s dns 4.19.9 False False True 4m45s DNS "default" is unavailable. image-registry False True True 3m57s Available: The deployment does not have available replicas... ingress False True True 4m29s 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 4m36s kube-controller-manager 4.19.9 True False False 4m36s kube-scheduler 4.19.9 True False False 4m36s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m20s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m39s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m36s openshift-controller-manager 4.19.9 True False False 4m36s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m39s operator-lifecycle-manager-catalog 4.19.9 True False False 4m31s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m36s service-ca storage 4.19.9 False False False 4m35s 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 5m48s dns 4.19.9 False False True 5m45s DNS "default" is unavailable. image-registry False True True 4m57s Available: The deployment does not have available replicas... ingress False True True 5m29s 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 5m36s kube-controller-manager 4.19.9 True False False 5m36s kube-scheduler 4.19.9 True False False 5m36s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m20s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 5m39s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m36s openshift-controller-manager 4.19.9 True False False 5m36s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m39s operator-lifecycle-manager-catalog 4.19.9 True False False 5m31s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m36s service-ca storage 4.19.9 False False False 5m35s 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 6m49s dns 4.19.9 False False True 6m46s DNS "default" is unavailable. image-registry False True True 5m58s Available: The deployment does not have available replicas... ingress False True True 6m30s 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 6m37s kube-controller-manager 4.19.9 True False False 6m37s kube-scheduler 4.19.9 True False False 6m37s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m21s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 6m40s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 6m37s openshift-controller-manager 4.19.9 True False False 6m37s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m40s operator-lifecycle-manager-catalog 4.19.9 True False False 6m32s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m37s service-ca storage 4.19.9 False False False 6m36s 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 7m49s dns 4.19.9 False True True 7m46s DNS "default" is unavailable. image-registry False True True 6m58s Available: The deployment does not have available replicas... ingress False True True 7m30s 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 7m37s kube-controller-manager 4.19.9 True False False 7m37s kube-scheduler 4.19.9 True False False 7m37s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m21s DaemonSet "/openshift-network-operator/iptables-alerter" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 9s Waiting for 3/3 Profiles to be applied openshift-apiserver 4.19.9 True False False 7m37s openshift-controller-manager 4.19.9 True False False 7m37s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m40s operator-lifecycle-manager-catalog 4.19.9 True False False 7m32s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m37s service-ca storage 4.19.9 True True False 11s 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 csi-snapshot-controller 4.19.9 True False False 8m49s dns 4.19.9 False False True 8m46s DNS "default" is unavailable. image-registry False True True 7m58s Available: The deployment does not have available replicas... ingress False True True 8m30s 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 8m37s kube-controller-manager 4.19.9 True False False 8m37s kube-scheduler 4.19.9 True False False 8m37s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m21s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes)... node-tuning 4.19.9 True False False 69s openshift-apiserver 4.19.9 True False False 8m37s openshift-controller-manager 4.19.9 True False False 8m37s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m40s operator-lifecycle-manager-catalog 4.19.9 True False False 8m32s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m37s service-ca storage 4.19.9 True False False 71s 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 9m50s dns 4.19.9 False True True 9m47s DNS "default" is unavailable. image-registry False True True 8m59s Available: The deployment does not have available replicas... ingress False True True 9m31s 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 9m38s kube-controller-manager 4.19.9 True False False 9m38s kube-scheduler 4.19.9 True False False 9m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 9m22s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes)... node-tuning 4.19.9 True False False 2m10s openshift-apiserver 4.19.9 True False False 9m38s openshift-controller-manager 4.19.9 True False False 9m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 9m41s operator-lifecycle-manager-catalog 4.19.9 True False False 9m33s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m38s service-ca storage 4.19.9 True False False 2m12s 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 True True 10m DNS "default" is unavailable. image-registry False True True 9m59s 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 10m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes)... node-tuning 4.19.9 True False False 3m10s 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 3m12s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 False True False 8s DeploymentAvailable: 0 replicas available for console deployment csi-snapshot-controller 4.19.9 True False False 11m dns 4.19.9 False True True 11m DNS "default" is unavailable. image-registry False True True 10m Available: The deployment does not have available replicas... 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 44s 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 40s monitoring Unknown True Unknown 12s Rolling out the stack. network 4.19.9 True True False 11m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.19.9 True False False 4m10s openshift-apiserver 4.19.9 True False False 11m openshift-controller-manager 4.19.9 True False False 11m openshift-samples 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 41s storage 4.19.9 True False False 4m12s 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 9s 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 True False 6s DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3." image-registry True True False 4s Progressing: The deployment has not completed... ingress 4.19.9 True True False 42s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 104s 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 100s monitoring Unknown True Unknown 72s Rolling out the stack. network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 5m10s openshift-apiserver 4.19.9 True False False 12m openshift-controller-manager 4.19.9 True False False 12m openshift-samples False False False 6s SampleUpsertsPending 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 101s storage 4.19.9 True False False 5m12s 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 70s 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 67s image-registry 4.19.9 True False False 65s ingress 4.19.9 True True False 103s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 2m45s 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 2m41s monitoring 4.19.9 True False False 9s network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 6m11s 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 58s 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 2m42s storage 4.19.9 True False False 6m13s 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 2m10s csi-snapshot-controller 4.19.9 True False False 14m dns 4.19.9 True False False 2m7s image-registry 4.19.9 True False False 2m5s ingress 4.19.9 True True False 2m43s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 3m45s 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 3m41s monitoring 4.19.9 True False False 69s network 4.19.9 True False False 14m node-tuning 4.19.9 True False False 7m11s 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 118s 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 3m42s storage 4.19.9 True False False 7m13s 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 3m10s csi-snapshot-controller 4.19.9 True False False 15m dns 4.19.9 True False False 3m7s image-registry 4.19.9 True False False 3m5s ingress 4.19.9 True True False 3m43s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 4m45s 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 4m41s monitoring 4.19.9 True False False 2m9s network 4.19.9 True False False 15m node-tuning 4.19.9 True False False 8m11s 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 2m58s 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 4m42s storage 4.19.9 True False False 8m13s 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 4m10s csi-snapshot-controller 4.19.9 True False False 16m dns 4.19.9 True False False 4m7s image-registry 4.19.9 True False False 4m5s ingress 4.19.9 True True False 4m43s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 5m45s 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 5m41s monitoring 4.19.9 True False False 3m9s network 4.19.9 True False False 16m node-tuning 4.19.9 True False False 9m11s 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 3m58s 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 5m42s storage 4.19.9 True False False 9m13s 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 5m11s csi-snapshot-controller 4.19.9 True False False 17m dns 4.19.9 True False False 5m8s image-registry 4.19.9 True False False 5m6s ingress 4.19.9 True True False 5m44s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 6m46s 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 6m42s monitoring 4.19.9 True False False 4m10s network 4.19.9 True False False 17m node-tuning 4.19.9 True False False 10m 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 4m59s 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 6m43s storage 4.19.9 True False False 10m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!