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 'konflux-ci-418295695583' 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-7dc266d539' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-7dc266d539' 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-7dc266d539 Domain Prefix: kx-7dc266d539 Display Name: kx-7dc266d539 ID: 2m94jei6fbj5hh7t43l8gogpi9fershv External ID: ecdc39c9-4e13-407a-8db3-071246bf844e Control Plane: ROSA Service Hosted OpenShift Version: 4.17.42 Channel Group: stable DNS: Not ready AWS Account: 418295695583 AWS Billing Account: 418295695583 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-001fc23497e4a3aeb, subnet-00ffba09365a434bc, subnet-074cbf0329958194a, subnet-0689cd077699b690a, subnet-0f9f09e46f74cde64, subnet-033f48892ddbaa09d EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 31 2025 11:04:29 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34pRkUzog66Sm5prqtLBaDluTZd OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (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-7dc266d539'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-7dc266d539 --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-7dc266d539' 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-7dc266d539 Version 2025-10-31 11:09:17 +0000 UTC hostedclusters kx-7dc266d539 ValidAWSIdentityProvider StatusUnknown 2025-10-31 11:09:18 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-31 11:09:18 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Condition not found in the CVO. 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Condition not found in the CVO. 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Condition not found in the CVO. 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Condition not found in the CVO. 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Condition not found in the CVO. 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Ignition server deployment not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 HostedCluster is supported by operator configuration 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Release image is valid 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Reconciliation active on resource 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is not found 2025-10-31 11:09:22 +0000 UTC hostedclusters kx-7dc266d539 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 11:09:23 +0000 UTC hostedclusters kx-7dc266d539 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 11:10:48 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-31 11:10:54 +0000 UTC hostedclusters kx-7dc266d539 Configuration passes validation 2025-10-31 11:10:55 +0000 UTC hostedclusters kx-7dc266d539 Required platform credentials are found 2025-10-31 11:10:59 +0000 UTC hostedclusters kx-7dc266d539 OIDC configuration is valid 2025-10-31 11:10:59 +0000 UTC hostedclusters kx-7dc266d539 Reconciliation completed successfully 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 AWS KMS is not configured 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 capi-provider deployment has 1 unavailable replicas 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 lookup api.kx-7dc266d539.dsug.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 Configuration passes validation 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 Waiting for etcd to reach quorum 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 Kube APIServer deployment not found 2025-10-31 11:11:11 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:11:25 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:11:30 +0000 UTC hostedclusters kx-7dc266d539 WebIdentityErr 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-7dc266d539 Version 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Reconciliation active on resource 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Get "https://a67d38f0fd704411ba20eed617e70db1-127cd2f60d23520d.elb.us-east-1.amazonaws.com:443/healthz": dial tcp: lookup a67d38f0fd704411ba20eed617e70db1-127cd2f60d23520d.elb.us-east-1.amazonaws.com on 172.30.0.10:53: no such host 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 Release image is valid 2025-10-31 11:09:21 +0000 UTC hostedclusters kx-7dc266d539 HostedCluster is supported by operator configuration 2025-10-31 11:09:22 +0000 UTC hostedclusters kx-7dc266d539 HostedCluster is at expected version 2025-10-31 11:10:48 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-31 11:10:54 +0000 UTC hostedclusters kx-7dc266d539 Configuration passes validation 2025-10-31 11:10:55 +0000 UTC hostedclusters kx-7dc266d539 Required platform credentials are found 2025-10-31 11:10:59 +0000 UTC hostedclusters kx-7dc266d539 Reconciliation completed successfully 2025-10-31 11:10:59 +0000 UTC hostedclusters kx-7dc266d539 OIDC configuration is valid 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 Configuration passes validation 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 AWS KMS is not configured 2025-10-31 11:11:01 +0000 UTC hostedclusters kx-7dc266d539 [capi-provider deployment has 2 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, oauth-openshift deployment has 2 unavailable replicas, router deployment has 2 unavailable replicas] 2025-10-31 11:11:11 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:11:25 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:11:56 +0000 UTC hostedclusters kx-7dc266d539 EtcdAvailable QuorumAvailable 2025-10-31 11:12:21 +0000 UTC hostedclusters kx-7dc266d539 Kube APIServer deployment is available 2025-10-31 11:12:43 +0000 UTC hostedclusters kx-7dc266d539 Ignition server deployment is available 2025-10-31 11:12:58 +0000 UTC hostedclusters kx-7dc266d539 Working towards 4.17.42: 349 of 621 done (56% complete) 2025-10-31 11:12:58 +0000 UTC hostedclusters kx-7dc266d539 ClusterVersionSucceeding FromClusterVersion 2025-10-31 11:12:58 +0000 UTC hostedclusters kx-7dc266d539 Condition not found in the CVO. 2025-10-31 11:12:58 +0000 UTC hostedclusters kx-7dc266d539 ClusterVersionAvailable FromClusterVersion 2025-10-31 11:12:58 +0000 UTC hostedclusters kx-7dc266d539 Payload loaded version="4.17.42" image="quay.io/openshift-release-dev/ocp-release@sha256:9b7b9909a1f064d5238f35f6e5fc9ac275a0d463a74e8c545544755d953a46d9" architecture="Multi" 2025-10-31 11:13:01 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:13 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:13 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:13 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:13 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:13 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:13 +0000 UTC hostedclusters kx-7dc266d539 All is well 2025-10-31 11:13:36 +0000 UTC hostedclusters kx-7dc266d539 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-31 11:13:50 +0000 UTC hostedclusters kx-7dc266d539 The hosted control plane is available INFO: Cluster 'kx-7dc266d539' 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.17.42 True False False 4m33s dns 4.17.42 False False True 4m34s DNS "default" is unavailable. image-registry False True True 4m24s Available: The deployment does not have available replicas... ingress False True True 4m17s 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.17.42 True False False 4m29s kube-controller-manager 4.17.42 True False False 4m29s kube-scheduler 4.17.42 True False False 4m29s kube-storage-version-migrator monitoring network 4.17.42 True True False 4m10s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 4m29s openshift-controller-manager 4.17.42 True False False 4m29s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m30s operator-lifecycle-manager-catalog 4.17.42 True False False 4m26s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m29s service-ca storage 4.17.42 False False False 4m29s 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.17.42 True False False 4m34s dns 4.17.42 False False True 4m35s DNS "default" is unavailable. image-registry False True True 4m25s Available: The deployment does not have available replicas... ingress False True True 4m18s 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.17.42 True False False 4m30s kube-controller-manager 4.17.42 True False False 4m30s kube-scheduler 4.17.42 True False False 4m30s kube-storage-version-migrator monitoring network 4.17.42 True True False 4m11s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m28s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 4m30s openshift-controller-manager 4.17.42 True False False 4m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m31s operator-lifecycle-manager-catalog 4.17.42 True False False 4m27s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m30s service-ca storage 4.17.42 False False False 4m30s 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.17.42 True False False 5m34s dns 4.17.42 False False True 5m35s DNS "default" is unavailable. image-registry False True True 5m25s Available: The deployment does not have available replicas... ingress False True True 5m18s 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.17.42 True False False 5m30s kube-controller-manager 4.17.42 True False False 5m30s kube-scheduler 4.17.42 True False False 5m30s kube-storage-version-migrator monitoring network 4.17.42 True True False 5m11s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 5m28s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 5m30s openshift-controller-manager 4.17.42 True False False 5m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 5m31s operator-lifecycle-manager-catalog 4.17.42 True False False 5m27s operator-lifecycle-manager-packageserver 4.17.42 True False False 5m30s service-ca storage 4.17.42 False False False 5m30s 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.17.42 True False False 6m34s dns 4.17.42 False False True 6m35s DNS "default" is unavailable. image-registry False True True 6m25s Available: The deployment does not have available replicas... ingress False True True 6m18s 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.17.42 True False False 6m30s kube-controller-manager 4.17.42 True False False 6m30s kube-scheduler 4.17.42 True False False 6m30s kube-storage-version-migrator monitoring network 4.17.42 True True False 6m11s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 6m28s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 6m30s openshift-controller-manager 4.17.42 True False False 6m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 6m31s operator-lifecycle-manager-catalog 4.17.42 True False False 6m27s operator-lifecycle-manager-packageserver 4.17.42 True False False 6m30s service-ca storage 4.17.42 False False False 6m30s 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.17.42 True False False 7m34s dns 4.17.42 False False True 7m35s DNS "default" is unavailable. image-registry False True True 7m25s Available: The deployment does not have available replicas... ingress False True True 7m18s 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.17.42 True False False 7m30s kube-controller-manager 4.17.42 True False False 7m30s kube-scheduler 4.17.42 True False False 7m30s kube-storage-version-migrator monitoring network 4.17.42 True True False 7m11s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 7m28s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 7m30s openshift-controller-manager 4.17.42 True False False 7m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 7m31s operator-lifecycle-manager-catalog 4.17.42 True False False 7m27s operator-lifecycle-manager-packageserver 4.17.42 True False False 7m30s service-ca storage 4.17.42 False False False 7m30s 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.17.42 True False False 8m34s dns 4.17.42 False False True 8m35s DNS "default" is unavailable. image-registry False True True 8m25s Available: The deployment does not have available replicas... ingress False True True 8m18s 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.17.42 True False False 9s kube-apiserver 4.17.42 True False False 8m30s kube-controller-manager 4.17.42 True False False 8m30s kube-scheduler 4.17.42 True False False 8m30s kube-storage-version-migrator 4.17.42 True False False 8s monitoring network 4.17.42 True True False 8m11s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True False False 30s openshift-apiserver 4.17.42 True False False 8m30s openshift-controller-manager 4.17.42 True False False 8m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 8m31s operator-lifecycle-manager-catalog 4.17.42 True False False 8m27s operator-lifecycle-manager-packageserver 4.17.42 True False False 8m30s service-ca 4.17.42 True False False 7s storage 4.17.42 True False False 27s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 24s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 9m35s dns 4.17.42 True False False 24s image-registry False True True 9m26s Available: The deployment does not have available replicas... ingress 4.17.42 True True False 11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.17.42 True False False 70s kube-apiserver 4.17.42 True False False 9m31s kube-controller-manager 4.17.42 True False False 9m31s kube-scheduler 4.17.42 True False False 9m31s kube-storage-version-migrator 4.17.42 True False False 69s monitoring Unknown True Unknown 44s Rolling out the stack. network 4.17.42 True False False 9m12s node-tuning 4.17.42 True False False 91s openshift-apiserver 4.17.42 True False False 9m31s openshift-controller-manager 4.17.42 True False False 9m31s openshift-samples 4.17.42 True False False 8s operator-lifecycle-manager 4.17.42 True False False 9m32s operator-lifecycle-manager-catalog 4.17.42 True False False 9m28s operator-lifecycle-manager-packageserver 4.17.42 True False False 9m31s service-ca 4.17.42 True False False 68s storage 4.17.42 True False False 88s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 84s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 10m dns 4.17.42 True False False 84s image-registry True True False 51s Progressing: The deployment has not completed... ingress 4.17.42 False True False 20s 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.17.42 True False False 2m10s kube-apiserver 4.17.42 True False False 10m kube-controller-manager 4.17.42 True False False 10m kube-scheduler 4.17.42 True False False 10m kube-storage-version-migrator 4.17.42 True False False 2m9s monitoring Unknown True Unknown 104s Rolling out the stack. network 4.17.42 True False False 10m node-tuning 4.17.42 True False False 2m31s openshift-apiserver 4.17.42 True False False 10m openshift-controller-manager 4.17.42 True False False 10m openshift-samples 4.17.42 True False False 68s operator-lifecycle-manager 4.17.42 True False False 10m operator-lifecycle-manager-catalog 4.17.42 True False False 10m operator-lifecycle-manager-packageserver 4.17.42 True False False 10m service-ca 4.17.42 True False False 2m8s storage 4.17.42 True False False 2m28s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 2m24s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 11m dns 4.17.42 True False False 2m24s image-registry True True True 111s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 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 old replica(s) are pending termination...... insights 4.17.42 True False False 3m10s kube-apiserver 4.17.42 True False False 11m kube-controller-manager 4.17.42 True False False 11m kube-scheduler 4.17.42 True False False 11m kube-storage-version-migrator 4.17.42 True False False 3m9s monitoring Unknown True Unknown 2m44s Rolling out the stack. network 4.17.42 True False False 11m node-tuning 4.17.42 True False False 3m31s openshift-apiserver 4.17.42 True False False 11m openshift-controller-manager 4.17.42 True False False 11m openshift-samples 4.17.42 True False False 2m8s operator-lifecycle-manager 4.17.42 True False False 11m operator-lifecycle-manager-catalog 4.17.42 True False False 11m operator-lifecycle-manager-packageserver 4.17.42 True False False 11m service-ca 4.17.42 True False False 3m8s storage 4.17.42 True False False 3m28s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 3m24s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 12m dns 4.17.42 True False False 3m24s image-registry True True True 2m51s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 False True False 20s 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.17.42 True False False 4m10s kube-apiserver 4.17.42 True False False 12m kube-controller-manager 4.17.42 True False False 12m kube-scheduler 4.17.42 True False False 12m kube-storage-version-migrator 4.17.42 True False False 4m9s monitoring Unknown True Unknown 3m44s Rolling out the stack. network 4.17.42 True False False 12m node-tuning 4.17.42 True False False 4m31s openshift-apiserver 4.17.42 True False False 12m openshift-controller-manager 4.17.42 True False False 12m openshift-samples 4.17.42 True False False 3m8s operator-lifecycle-manager 4.17.42 True False False 12m operator-lifecycle-manager-catalog 4.17.42 True False False 12m operator-lifecycle-manager-packageserver 4.17.42 True False False 12m service-ca 4.17.42 True False False 4m8s storage 4.17.42 True False False 4m28s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 4m24s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 13m dns 4.17.42 True False False 4m24s image-registry True True True 3m51s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 True True False 1s 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.17.42 True False False 5m10s kube-apiserver 4.17.42 True False False 13m kube-controller-manager 4.17.42 True False False 13m kube-scheduler 4.17.42 True False False 13m kube-storage-version-migrator 4.17.42 True False False 5m9s monitoring Unknown True Unknown 4m44s Rolling out the stack. network 4.17.42 True False False 13m node-tuning 4.17.42 True False False 5m31s openshift-apiserver 4.17.42 True False False 13m openshift-controller-manager 4.17.42 True False False 13m openshift-samples 4.17.42 True False False 4m8s operator-lifecycle-manager 4.17.42 True False False 13m operator-lifecycle-manager-catalog 4.17.42 True False False 13m operator-lifecycle-manager-packageserver 4.17.42 True False False 13m service-ca 4.17.42 True False False 5m8s storage 4.17.42 True False False 5m28s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 5m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 14m dns 4.17.42 True False False 5m25s image-registry True True True 4m52s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 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.17.42 True False False 6m11s kube-apiserver 4.17.42 True False False 14m kube-controller-manager 4.17.42 True False False 14m kube-scheduler 4.17.42 True False False 14m kube-storage-version-migrator 4.17.42 True False False 6m10s monitoring Unknown True Unknown 5m45s Rolling out the stack. network 4.17.42 True False False 14m node-tuning 4.17.42 True False False 6m32s openshift-apiserver 4.17.42 True False False 14m openshift-controller-manager 4.17.42 True False False 14m openshift-samples 4.17.42 True False False 5m9s operator-lifecycle-manager 4.17.42 True False False 14m operator-lifecycle-manager-catalog 4.17.42 True False False 14m operator-lifecycle-manager-packageserver 4.17.42 True False False 14m service-ca 4.17.42 True False False 6m9s storage 4.17.42 True False False 6m29s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 6m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 15m dns 4.17.42 True False False 6m25s image-registry True True True 5m52s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 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.17.42 True False False 7m11s kube-apiserver 4.17.42 True False False 15m kube-controller-manager 4.17.42 True False False 15m kube-scheduler 4.17.42 True False False 15m kube-storage-version-migrator 4.17.42 True False False 7m10s monitoring Unknown True Unknown 6m45s Rolling out the stack. network 4.17.42 True True False 15m Deployment "management/ocm-production-2m94jei6fbj5hh7t43l8gogpi9fershv-kx-7dc266d539/network-node-identity" is not available (awaiting 1 nodes) node-tuning 4.17.42 True False False 7m32s openshift-apiserver 4.17.42 True False False 15m openshift-controller-manager 4.17.42 True False False 15m openshift-samples 4.17.42 True False False 6m9s operator-lifecycle-manager 4.17.42 True False False 15m operator-lifecycle-manager-catalog 4.17.42 True False False 15m operator-lifecycle-manager-packageserver 4.17.42 True False False 15m service-ca 4.17.42 True False False 7m9s storage 4.17.42 True False False 7m29s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 7m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 16m dns 4.17.42 True False False 7m25s image-registry True True True 6m52s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 True True False 3m2s 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.17.42 True False False 8m11s kube-apiserver 4.17.42 True False False 16m kube-controller-manager 4.17.42 True False False 16m kube-scheduler 4.17.42 True False False 16m kube-storage-version-migrator 4.17.42 True False False 8m10s monitoring Unknown True Unknown 7m45s Rolling out the stack. network 4.17.42 True True False 16m Deployment "management/ocm-production-2m94jei6fbj5hh7t43l8gogpi9fershv-kx-7dc266d539/network-node-identity" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True False False 8m32s openshift-apiserver 4.17.42 True False False 16m openshift-controller-manager 4.17.42 True False False 16m openshift-samples 4.17.42 True False False 7m9s operator-lifecycle-manager 4.17.42 True False False 16m operator-lifecycle-manager-catalog 4.17.42 True False False 16m operator-lifecycle-manager-packageserver 4.17.42 True False False 16m service-ca 4.17.42 True False False 8m9s storage 4.17.42 False True False 51s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverControllerServiceControllerAvailable: Waiting for Deployment Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 8m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 17m dns 4.17.42 True False False 8m25s image-registry True True True 7m52s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 True True False 4m2s 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.17.42 True False False 9m11s kube-apiserver 4.17.42 True False False 17m kube-controller-manager 4.17.42 True False False 17m kube-scheduler 4.17.42 True False False 17m kube-storage-version-migrator 4.17.42 True False False 9m10s monitoring Unknown True Unknown 8m45s Rolling out the stack. network 4.17.42 True True False 17m Deployment "management/ocm-production-2m94jei6fbj5hh7t43l8gogpi9fershv-kx-7dc266d539/multus-admission-controller" is not available (awaiting 1 nodes) node-tuning 4.17.42 True False False 9m32s openshift-apiserver 4.17.42 True False False 17m openshift-controller-manager 4.17.42 True False False 17m openshift-samples 4.17.42 True False False 8m9s operator-lifecycle-manager 4.17.42 True False False 17m operator-lifecycle-manager-catalog 4.17.42 True False False 17m operator-lifecycle-manager-packageserver 4.17.42 True False False 17m service-ca 4.17.42 True False False 9m9s storage 4.17.42 True False False 32s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 9m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 18m dns 4.17.42 True True False 9m26s DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2." image-registry True True True 8m53s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 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.17.42 True False False 10m kube-apiserver 4.17.42 True False False 18m kube-controller-manager 4.17.42 True False False 18m kube-scheduler 4.17.42 True False False 18m kube-storage-version-migrator 4.17.42 True False False 10m monitoring Unknown True Unknown 9m46s Rolling out the stack. network 4.17.42 True True False 18m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)... node-tuning 4.17.42 True True False 40s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 18m openshift-controller-manager 4.17.42 True False False 18m openshift-samples 4.17.42 True False False 9m10s operator-lifecycle-manager 4.17.42 True False False 18m operator-lifecycle-manager-catalog 4.17.42 True False False 18m operator-lifecycle-manager-packageserver 4.17.42 True False False 18m service-ca 4.17.42 True False False 10m storage 4.17.42 True True False 93s 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.17.42 True True False 10m SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 19m dns 4.17.42 True True False 10m DNS "default" reports Progressing=True: "Have 1 available DNS pods, want 2.\nHave 2 available node-resolver pods, want 3." image-registry True True True 9m53s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-64cdb7f9d9" has timed out progressing. ingress 4.17.42 True True False 6m3s 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.17.42 True False False 11m kube-apiserver 4.17.42 True False False 19m kube-controller-manager 4.17.42 True False False 19m kube-scheduler 4.17.42 True False False 19m kube-storage-version-migrator 4.17.42 True False False 11m monitoring Unknown True Unknown 10m Rolling out the stack. network 4.17.42 True True False 19m DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.17.42 True True False 13s Waiting for 1/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 19m openshift-controller-manager 4.17.42 True False False 19m openshift-samples 4.17.42 True False False 10m operator-lifecycle-manager 4.17.42 True False False 19m operator-lifecycle-manager-catalog 4.17.42 True False False 19m operator-lifecycle-manager-packageserver 4.17.42 True False False 19m service-ca 4.17.42 True False False 11m storage 4.17.42 True True False 2m33s 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.17.42 True False False 11m csi-snapshot-controller 4.17.42 True False False 20m dns 4.17.42 True False False 11m image-registry 4.17.42 True False False 10m ingress 4.17.42 True False False 7m3s insights 4.17.42 True False False 12m kube-apiserver 4.17.42 True False False 20m kube-controller-manager 4.17.42 True False False 20m kube-scheduler 4.17.42 True False False 20m kube-storage-version-migrator 4.17.42 True False False 12m monitoring Unknown True Unknown 11m Rolling out the stack. network 4.17.42 True False False 20m node-tuning 4.17.42 True False False 73s openshift-apiserver 4.17.42 True False False 20m openshift-controller-manager 4.17.42 True False False 20m openshift-samples 4.17.42 True False False 11m operator-lifecycle-manager 4.17.42 True False False 20m operator-lifecycle-manager-catalog 4.17.42 True False False 20m operator-lifecycle-manager-packageserver 4.17.42 True False False 20m service-ca 4.17.42 True False False 12m storage 4.17.42 True False False 3m33s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 12m csi-snapshot-controller 4.17.42 True False False 21m dns 4.17.42 True False False 12m image-registry 4.17.42 True False False 11m ingress 4.17.42 True False False 8m3s insights 4.17.42 True False False 13m kube-apiserver 4.17.42 True False False 21m kube-controller-manager 4.17.42 True False False 21m kube-scheduler 4.17.42 True False False 21m kube-storage-version-migrator 4.17.42 True False False 13m monitoring Unknown True Unknown 12m Rolling out the stack. network 4.17.42 True False False 21m node-tuning 4.17.42 True False False 2m13s openshift-apiserver 4.17.42 True False False 21m openshift-controller-manager 4.17.42 True False False 21m openshift-samples 4.17.42 True False False 12m operator-lifecycle-manager 4.17.42 True False False 21m operator-lifecycle-manager-catalog 4.17.42 True False False 21m operator-lifecycle-manager-packageserver 4.17.42 True False False 21m service-ca 4.17.42 True False False 13m storage 4.17.42 True False False 4m33s Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!