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-df1dbdc39d' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-df1dbdc39d' 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-df1dbdc39d Domain Prefix: kx-df1dbdc39d Display Name: kx-df1dbdc39d ID: 2m4d47n06vnnar8irosqeis6p3r97d34 External ID: 28cd5e67-bf7c-4ba7-8763-ec5169f15b18 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 24 2025 06:43:48 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34VABIyVHBPwMygZbvbhcd17k32 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-df1dbdc39d'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-df1dbdc39d --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-df1dbdc39d' 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-df1dbdc39d Version 2025-10-24 06:48:21 +0000 UTC hostedclusters kx-df1dbdc39d ValidAWSIdentityProvider StatusUnknown 2025-10-24 06:48:22 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-24 06:48:22 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Ignition server deployment not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d HostedCluster is supported by operator configuration 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Release image is valid 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Reconciliation active on resource 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Ignition server deployment not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d HostedCluster is supported by operator configuration 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Release image is valid 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Reconciliation active on resource 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Ignition server deployment not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d HostedCluster is supported by operator configuration 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Release image is valid 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Reconciliation active on resource 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Ignition server deployment not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d HostedCluster is supported by operator configuration 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Release image is valid 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Reconciliation active on resource 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d 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-df1dbdc39d Version 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Release image is valid 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Waiting for hosted control plane kubeconfig to be created 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d HostedCluster is at expected version 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d HostedCluster is supported by operator configuration 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Ignition server deployment not found 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Reconciliation active on resource 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:48:25 +0000 UTC hostedclusters kx-df1dbdc39d Condition not found in the CVO. 2025-10-24 06:49:53 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-24 06:50:02 +0000 UTC hostedclusters kx-df1dbdc39d Configuration passes validation 2025-10-24 06:50:04 +0000 UTC hostedclusters kx-df1dbdc39d Required platform credentials are found 2025-10-24 06:50:09 +0000 UTC hostedclusters kx-df1dbdc39d OIDC configuration is valid 2025-10-24 06:50:09 +0000 UTC hostedclusters kx-df1dbdc39d Reconciliation completed successfully 2025-10-24 06:50:13 +0000 UTC hostedclusters kx-df1dbdc39d AWS KMS is not configured 2025-10-24 06:50:13 +0000 UTC hostedclusters kx-df1dbdc39d capi-provider deployment has 2 unavailable replicas 2025-10-24 06:50:13 +0000 UTC hostedclusters kx-df1dbdc39d lookup api.kx-df1dbdc39d.e6zv.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-24 06:50:13 +0000 UTC hostedclusters kx-df1dbdc39d Configuration passes validation 2025-10-24 06:50:13 +0000 UTC hostedclusters kx-df1dbdc39d Waiting for etcd to reach quorum 2025-10-24 06:50:13 +0000 UTC hostedclusters kx-df1dbdc39d Kube APIServer deployment not found 2025-10-24 06:50:35 +0000 UTC hostedclusters kx-df1dbdc39d All is well 2025-10-24 06:50:35 +0000 UTC hostedclusters kx-df1dbdc39d All is well 2025-10-24 06:50:41 +0000 UTC hostedclusters kx-df1dbdc39d WebIdentityErr 2025-10-24 06:50:57 +0000 UTC hostedclusters kx-df1dbdc39d EtcdAvailable QuorumAvailable 2025-10-24 06:51:46 +0000 UTC hostedclusters kx-df1dbdc39d Kube APIServer deployment is available 2025-10-24 06:52:12 +0000 UTC hostedclusters kx-df1dbdc39d All is well 2025-10-24 06:52:14 +0000 UTC hostedclusters kx-df1dbdc39d All is well 2025-10-24 06:52:16 +0000 UTC hostedclusters kx-df1dbdc39d Ignition server deployment is available 2025-10-24 06:52:41 +0000 UTC hostedclusters kx-df1dbdc39d ClusterVersionSucceeding FromClusterVersion 2025-10-24 06:52:41 +0000 UTC hostedclusters kx-df1dbdc39d ClusterVersionAvailable FromClusterVersion 2025-10-24 06:52:41 +0000 UTC hostedclusters kx-df1dbdc39d lookup api.kx-df1dbdc39d.e6zv.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-24 06:52:41 +0000 UTC hostedclusters kx-df1dbdc39d Working towards 4.19.9: 278 of 629 done (44% complete) 2025-10-24 06:52:41 +0000 UTC hostedclusters kx-df1dbdc39d Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-24 06:52:48 +0000 UTC hostedclusters kx-df1dbdc39d An update is already in progress and the details are in the Progressing condition 2025-10-24 06:53:00 +0000 UTC hostedclusters kx-df1dbdc39d The hosted control plane is available INFO: Cluster 'kx-df1dbdc39d' 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 3m14s dns 4.19.9 False False True 3m14s DNS "default" is unavailable. image-registry False True True 3m3s Available: The deployment does not have available replicas... ingress False True True 2m57s 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 3m7s kube-controller-manager 4.19.9 True False False 3m7s kube-scheduler 4.19.9 True False False 3m7s kube-storage-version-migrator monitoring network 4.19.9 True True False 2m43s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 3m5s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m7s openshift-controller-manager 4.19.9 True False False 3m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m9s operator-lifecycle-manager-catalog 4.19.9 True False False 3m7s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m7s service-ca storage 4.19.9 False False False 3m7s 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 3m14s dns 4.19.9 False False True 3m14s DNS "default" is unavailable. image-registry False True True 3m3s Available: The deployment does not have available replicas... ingress False True True 2m57s 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 3m7s kube-controller-manager 4.19.9 True False False 3m7s kube-scheduler 4.19.9 True False False 3m7s kube-storage-version-migrator monitoring network 4.19.9 True True False 2m43s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 3m5s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m7s openshift-controller-manager 4.19.9 True False False 3m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m9s operator-lifecycle-manager-catalog 4.19.9 True False False 3m7s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m7s service-ca storage 4.19.9 False False False 3m7s 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 4m15s dns 4.19.9 False False True 4m15s DNS "default" is unavailable. image-registry False True True 4m4s Available: The deployment does not have available replicas... ingress False True True 3m58s 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 4m8s kube-controller-manager 4.19.9 True False False 4m8s kube-scheduler 4.19.9 True False False 4m8s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m44s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m8s openshift-controller-manager 4.19.9 True False False 4m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m10s operator-lifecycle-manager-catalog 4.19.9 True False False 4m8s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m8s service-ca storage 4.19.9 False False False 4m8s 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 5m15s dns 4.19.9 False False True 5m15s DNS "default" is unavailable. image-registry False True True 5m4s Available: The deployment does not have available replicas... ingress False True True 4m58s 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 5m8s kube-controller-manager 4.19.9 True False False 5m8s kube-scheduler 4.19.9 True False False 5m8s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m44s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 5m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m8s openshift-controller-manager 4.19.9 True False False 5m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m10s operator-lifecycle-manager-catalog 4.19.9 True False False 5m8s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m8s service-ca storage 4.19.9 False False False 5m8s 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 6m15s dns 4.19.9 False False True 6m15s DNS "default" is unavailable. image-registry False True True 6m4s Available: The deployment does not have available replicas... ingress False True True 5m58s 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 6m8s kube-controller-manager 4.19.9 True False False 6m8s kube-scheduler 4.19.9 True False False 6m8s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m44s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 6m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 6m8s openshift-controller-manager 4.19.9 True False False 6m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m10s operator-lifecycle-manager-catalog 4.19.9 True False False 6m8s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m8s service-ca storage 4.19.9 False False False 6m8s 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 7m15s dns 4.19.9 False False True 7m15s DNS "default" is unavailable. image-registry False True True 7m4s Available: The deployment does not have available replicas... ingress False True True 6m58s 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 7m8s kube-controller-manager 4.19.9 True False False 7m8s kube-scheduler 4.19.9 True False False 7m8s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m44s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 7m6s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 7m8s openshift-controller-manager 4.19.9 True False False 7m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m10s operator-lifecycle-manager-catalog 4.19.9 True False False 7m8s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m8s service-ca storage 4.19.9 False False False 7m8s 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 8m16s dns 4.19.9 False False True 8m16s DNS "default" is unavailable. image-registry False True True 8m5s Available: The deployment does not have available replicas... ingress False True True 7m59s 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 8m9s kube-controller-manager 4.19.9 True False False 8m9s kube-scheduler 4.19.9 True False False 8m9s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m45s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 8m7s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 8m9s openshift-controller-manager 4.19.9 True False False 8m9s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m11s operator-lifecycle-manager-catalog 4.19.9 True False False 8m9s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m9s service-ca storage 4.19.9 False False False 8m9s 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 9m16s dns 4.19.9 False False True 9m16s DNS "default" is unavailable. image-registry False True True 9m5s Available: The deployment does not have available replicas... ingress False True True 8m59s 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 9m9s kube-controller-manager 4.19.9 True False False 9m9s kube-scheduler 4.19.9 True False False 9m9s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m45s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 9m7s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 9m9s openshift-controller-manager 4.19.9 True False False 9m9s openshift-samples operator-lifecycle-manager 4.19.9 True False False 9m11s operator-lifecycle-manager-catalog 4.19.9 True False False 9m9s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m9s service-ca storage 4.19.9 False False False 9m9s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 10m dns 4.19.9 False False True 10m DNS "default" is unavailable. image-registry False True True 10m Available: The deployment does not have available replicas... ingress False True True 9m59s 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 9m45s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 10m DaemonSet "tuned" has no available Pod(s) 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 False False False 10m 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 11m dns 4.19.9 False False True 11m DNS "default" is unavailable. image-registry False True True 11m 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 11m kube-controller-manager 4.19.9 True False False 11m kube-scheduler 4.19.9 True False False 11m kube-storage-version-migrator monitoring network 4.19.9 True True False 10m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 11m DaemonSet "tuned" has no available Pod(s) 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 storage 4.19.9 False False False 11m 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 12m dns 4.19.9 False False True 12m DNS "default" is unavailable. image-registry False True True 12m Available: The deployment does not have available replicas... ingress False True True 12m 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 12m kube-controller-manager 4.19.9 True False False 12m kube-scheduler 4.19.9 True False False 12m kube-storage-version-migrator monitoring network 4.19.9 True True False 11m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.19.9 True False False 30s openshift-apiserver 4.19.9 True False False 12m openshift-controller-manager 4.19.9 True False False 12m openshift-samples 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 storage 4.19.9 True False False 27s 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 13m dns 4.19.9 False True True 13m DNS "default" is unavailable. image-registry False True True 13m Available: The deployment does not have available replicas... ingress False True True 13m 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 13m kube-controller-manager 4.19.9 True False False 13m kube-scheduler 4.19.9 True False False 13m kube-storage-version-migrator monitoring network 4.19.9 True True False 12m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.19.9 True False False 90s openshift-apiserver 4.19.9 True False False 13m openshift-controller-manager 4.19.9 True False False 13m openshift-samples 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 storage 4.19.9 True False False 87s 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 14m dns 4.19.9 False True True 14m DNS "default" is unavailable. image-registry False True True 14m Available: The deployment does not have available replicas... ingress False True True 14m 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 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 27s monitoring Unknown True Unknown 0s Rolling out the stack. network 4.19.9 True True False 13m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.19.9 True False False 2m30s openshift-apiserver 4.19.9 True False False 14m openshift-controller-manager 4.19.9 True False False 14m openshift-samples 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 27s storage 4.19.9 True False False 2m27s 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 24s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 15m dns 4.19.9 True False False 48s image-registry True True False 0s Progressing: The deployment has not completed... ingress 4.19.9 False True True 2s 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 90s 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 87s monitoring Unknown True Unknown 60s Rolling out the stack. network 4.19.9 True True False 14m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready node-tuning 4.19.9 True False False 3m30s 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 44s 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 87s storage 4.19.9 True False False 3m27s 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 85s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 16m dns 4.19.9 True False False 109s image-registry True True True 61s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 False True True 63s 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 2m31s 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 2m28s monitoring Unknown True Unknown 2m1s Rolling out the stack. network 4.19.9 True False False 15m node-tuning 4.19.9 True False False 4m31s 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 105s 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 2m28s storage 4.19.9 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.19.9 True True False 2m25s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 17m dns 4.19.9 True False False 2m49s image-registry True True True 2m1s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True True 43s 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 3m31s 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 3m28s monitoring Unknown True Unknown 3m1s Rolling out the stack. network 4.19.9 True False False 16m node-tuning 4.19.9 True False False 5m31s 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 2m45s 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 3m28s storage 4.19.9 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.19.9 True True False 3m25s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 18m dns 4.19.9 True False False 3m49s image-registry True True True 3m1s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True True 103s 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 4m31s kube-apiserver 4.19.9 True False False 18m kube-controller-manager 4.19.9 True False False 18m kube-scheduler 4.19.9 True False False 18m kube-storage-version-migrator 4.19.9 True False False 4m28s monitoring Unknown True Unknown 4m1s Rolling out the stack. network 4.19.9 True False False 17m node-tuning 4.19.9 True False False 6m31s openshift-apiserver 4.19.9 True False False 18m openshift-controller-manager 4.19.9 True False False 18m openshift-samples 4.19.9 True False False 3m45s operator-lifecycle-manager 4.19.9 True False False 18m operator-lifecycle-manager-catalog 4.19.9 True False False 18m operator-lifecycle-manager-packageserver 4.19.9 True False False 18m service-ca 4.19.9 True False False 4m28s storage 4.19.9 True False False 6m28s 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 4m25s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 19m dns 4.19.9 True False False 4m49s image-registry True True True 4m1s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. 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 of 2 updated replica(s) are available...... insights 4.19.9 True False False 5m31s kube-apiserver 4.19.9 True False False 19m kube-controller-manager 4.19.9 True False False 19m kube-scheduler 4.19.9 True False False 19m kube-storage-version-migrator 4.19.9 True False False 5m28s monitoring Unknown True Unknown 5m1s Rolling out the stack. network 4.19.9 True False False 18m node-tuning 4.19.9 True False False 7m31s openshift-apiserver 4.19.9 True False False 19m openshift-controller-manager 4.19.9 True False False 19m openshift-samples 4.19.9 True False False 4m45s operator-lifecycle-manager 4.19.9 True False False 19m operator-lifecycle-manager-catalog 4.19.9 True False False 19m operator-lifecycle-manager-packageserver 4.19.9 True False False 19m service-ca 4.19.9 True False False 5m28s storage 4.19.9 True False False 7m28s 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 5m26s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 20m dns 4.19.9 True False False 5m50s image-registry True True True 5m2s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 3m44s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 6m32s kube-apiserver 4.19.9 True False False 20m kube-controller-manager 4.19.9 True False False 20m kube-scheduler 4.19.9 True False False 20m kube-storage-version-migrator 4.19.9 True False False 6m29s monitoring Unknown True Unknown 6m2s Rolling out the stack. network 4.19.9 True False False 19m node-tuning 4.19.9 True False False 8m32s openshift-apiserver 4.19.9 True False False 20m openshift-controller-manager 4.19.9 True False False 20m openshift-samples 4.19.9 True False False 5m46s operator-lifecycle-manager 4.19.9 True False False 20m operator-lifecycle-manager-catalog 4.19.9 True False False 20m operator-lifecycle-manager-packageserver 4.19.9 True False False 20m service-ca 4.19.9 True False False 6m29s storage 4.19.9 True False False 8m29s 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 6m26s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 21m dns 4.19.9 True False False 6m50s image-registry True True True 6m2s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 4m44s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 7m32s kube-apiserver 4.19.9 True False False 21m kube-controller-manager 4.19.9 True False False 21m kube-scheduler 4.19.9 True False False 21m kube-storage-version-migrator 4.19.9 True False False 7m29s monitoring Unknown True Unknown 7m2s Rolling out the stack. network 4.19.9 True False False 20m node-tuning 4.19.9 True False False 9m32s openshift-apiserver 4.19.9 True False False 21m openshift-controller-manager 4.19.9 True False False 21m openshift-samples 4.19.9 True False False 6m46s operator-lifecycle-manager 4.19.9 True False False 21m operator-lifecycle-manager-catalog 4.19.9 True False False 21m operator-lifecycle-manager-packageserver 4.19.9 True False False 21m service-ca 4.19.9 True False False 7m29s storage 4.19.9 True False False 9m29s 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 7m26s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 22m dns 4.19.9 True False False 7m50s image-registry True True True 7m2s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. 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 of 2 updated replica(s) are available...... insights 4.19.9 True False False 8m32s kube-apiserver 4.19.9 True False False 22m kube-controller-manager 4.19.9 True False False 22m kube-scheduler 4.19.9 True False False 22m kube-storage-version-migrator 4.19.9 True False False 8m29s monitoring Unknown True Unknown 8m2s Rolling out the stack. network 4.19.9 True False False 21m node-tuning 4.19.9 True False False 10m openshift-apiserver 4.19.9 True False False 22m openshift-controller-manager 4.19.9 True False False 22m openshift-samples 4.19.9 True False False 7m46s operator-lifecycle-manager 4.19.9 True False False 22m operator-lifecycle-manager-catalog 4.19.9 True False False 22m operator-lifecycle-manager-packageserver 4.19.9 True False False 22m service-ca 4.19.9 True False False 8m29s storage 4.19.9 True False False 10m 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 8m26s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 23m dns 4.19.9 True False False 8m50s image-registry True True True 8m2s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 6m44s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 9m32s kube-apiserver 4.19.9 True False False 23m kube-controller-manager 4.19.9 True False False 23m kube-scheduler 4.19.9 True False False 23m kube-storage-version-migrator 4.19.9 True False False 9m29s monitoring Unknown True Unknown 9m2s Rolling out the stack. network 4.19.9 True False False 22m node-tuning 4.19.9 True False False 11m openshift-apiserver 4.19.9 True False False 23m openshift-controller-manager 4.19.9 True False False 23m openshift-samples 4.19.9 True False False 8m46s operator-lifecycle-manager 4.19.9 True False False 23m operator-lifecycle-manager-catalog 4.19.9 True False False 23m operator-lifecycle-manager-packageserver 4.19.9 True False False 23m service-ca 4.19.9 True False False 9m29s storage 4.19.9 True False False 11m 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 9m27s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 24m dns 4.19.9 True False False 9m51s image-registry True True True 9m3s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 7m45s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 10m kube-apiserver 4.19.9 True False False 24m kube-controller-manager 4.19.9 True False False 24m kube-scheduler 4.19.9 True False False 24m kube-storage-version-migrator 4.19.9 True False False 10m monitoring Unknown True Unknown 10m Rolling out the stack. network 4.19.9 True False False 23m node-tuning 4.19.9 True False False 12m openshift-apiserver 4.19.9 True False False 24m openshift-controller-manager 4.19.9 True False False 24m openshift-samples 4.19.9 True False False 9m47s operator-lifecycle-manager 4.19.9 True False False 24m operator-lifecycle-manager-catalog 4.19.9 True False False 24m operator-lifecycle-manager-packageserver 4.19.9 True False False 24m service-ca 4.19.9 True False False 10m storage 4.19.9 True False False 12m 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 10m SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 25m dns 4.19.9 True False False 10m image-registry True True True 10m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 8m45s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 11m kube-apiserver 4.19.9 True False False 25m kube-controller-manager 4.19.9 True False False 25m kube-scheduler 4.19.9 True False False 25m kube-storage-version-migrator 4.19.9 True False False 11m monitoring Unknown True Unknown 11m Rolling out the stack. network 4.19.9 True False False 24m node-tuning 4.19.9 True False False 13m openshift-apiserver 4.19.9 True False False 25m openshift-controller-manager 4.19.9 True False False 25m openshift-samples 4.19.9 True False False 10m operator-lifecycle-manager 4.19.9 True False False 25m operator-lifecycle-manager-catalog 4.19.9 True False False 25m operator-lifecycle-manager-packageserver 4.19.9 True False False 25m service-ca 4.19.9 True False False 11m storage 4.19.9 True False False 13m 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 11m SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 26m dns 4.19.9 True False False 11m image-registry True True True 11m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 9m45s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 12m kube-apiserver 4.19.9 True False False 26m kube-controller-manager 4.19.9 True False False 26m kube-scheduler 4.19.9 True False False 26m kube-storage-version-migrator 4.19.9 True False False 12m monitoring Unknown True Unknown 12m Rolling out the stack. network 4.19.9 True False False 25m node-tuning 4.19.9 True False False 14m openshift-apiserver 4.19.9 True False False 26m openshift-controller-manager 4.19.9 True False False 26m openshift-samples 4.19.9 True False False 11m operator-lifecycle-manager 4.19.9 True False False 26m operator-lifecycle-manager-catalog 4.19.9 True False False 26m operator-lifecycle-manager-packageserver 4.19.9 True False False 26m service-ca 4.19.9 True False False 12m storage 4.19.9 True False False 14m 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 12m SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 27m dns 4.19.9 True True False 12m DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2." image-registry True True True 12m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5b659655dd" has timed out progressing. ingress 4.19.9 True True False 10m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 13m kube-apiserver 4.19.9 True False False 27m kube-controller-manager 4.19.9 True False False 27m kube-scheduler 4.19.9 True False False 27m kube-storage-version-migrator 4.19.9 True False False 13m monitoring Unknown True Unknown 13m Rolling out the stack. network 4.19.9 True True False 26m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 0s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.19.9 True False False 27m openshift-controller-manager 4.19.9 True False False 27m openshift-samples 4.19.9 True False False 12m operator-lifecycle-manager 4.19.9 True False False 27m operator-lifecycle-manager-catalog 4.19.9 True False False 27m operator-lifecycle-manager-packageserver 4.19.9 True False False 27m service-ca 4.19.9 True False False 13m storage 4.19.9 True True False 15m AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 13m SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 28m dns 4.19.9 True False False 13m image-registry 4.19.9 True True False 13m Progressing: The deployment has not completed... ingress 4.19.9 True True False 11m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.19.9 True False False 14m kube-apiserver 4.19.9 True False False 28m kube-controller-manager 4.19.9 True False False 28m kube-scheduler 4.19.9 True False False 28m kube-storage-version-migrator 4.19.9 True False False 14m monitoring Unknown True Unknown 14m Rolling out the stack. network 4.19.9 True True False 27m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes) node-tuning 4.19.9 True False False 60s openshift-apiserver 4.19.9 True False False 28m openshift-controller-manager 4.19.9 True False False 28m openshift-samples 4.19.9 True False False 13m operator-lifecycle-manager 4.19.9 True False False 28m operator-lifecycle-manager-catalog 4.19.9 True False False 28m operator-lifecycle-manager-packageserver 4.19.9 True False False 28m service-ca 4.19.9 True False False 14m storage 4.19.9 True False False 16m 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 14m csi-snapshot-controller 4.19.9 True False False 29m dns 4.19.9 True False False 14m image-registry 4.19.9 True False False 14m ingress 4.19.9 True False False 12m insights 4.19.9 True False False 15m kube-apiserver 4.19.9 True False False 29m kube-controller-manager 4.19.9 True False False 29m kube-scheduler 4.19.9 True False False 29m kube-storage-version-migrator 4.19.9 True False False 15m monitoring Unknown True Unknown 15m Rolling out the stack. network 4.19.9 True False False 28m node-tuning 4.19.9 True False False 2m openshift-apiserver 4.19.9 True False False 29m openshift-controller-manager 4.19.9 True False False 29m openshift-samples 4.19.9 True False False 14m operator-lifecycle-manager 4.19.9 True False False 29m operator-lifecycle-manager-catalog 4.19.9 True False False 29m operator-lifecycle-manager-packageserver 4.19.9 True False False 29m service-ca 4.19.9 True False False 15m storage 4.19.9 True False False 17m 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 15m csi-snapshot-controller 4.19.9 True False False 30m dns 4.19.9 True False False 15m image-registry 4.19.9 True False False 15m ingress 4.19.9 True False False 13m insights 4.19.9 True False False 16m kube-apiserver 4.19.9 True False False 30m kube-controller-manager 4.19.9 True False False 30m kube-scheduler 4.19.9 True False False 30m kube-storage-version-migrator 4.19.9 True False False 16m monitoring 4.19.9 True False False 16s network 4.19.9 True False False 29m node-tuning 4.19.9 True False False 3m openshift-apiserver 4.19.9 True False False 30m openshift-controller-manager 4.19.9 True False False 30m openshift-samples 4.19.9 True False False 15m operator-lifecycle-manager 4.19.9 True False False 30m operator-lifecycle-manager-catalog 4.19.9 True False False 30m operator-lifecycle-manager-packageserver 4.19.9 True False False 30m service-ca 4.19.9 True False False 16m storage 4.19.9 True False False 18m 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 16m csi-snapshot-controller 4.19.9 True False False 31m dns 4.19.9 True False False 16m image-registry 4.19.9 True False False 16m ingress 4.19.9 True False False 14m insights 4.19.9 True False False 17m kube-apiserver 4.19.9 True False False 31m kube-controller-manager 4.19.9 True False False 31m kube-scheduler 4.19.9 True False False 31m kube-storage-version-migrator 4.19.9 True False False 17m monitoring 4.19.9 True False False 77s network 4.19.9 True False False 30m node-tuning 4.19.9 True False False 4m1s openshift-apiserver 4.19.9 True False False 31m openshift-controller-manager 4.19.9 True False False 31m openshift-samples 4.19.9 True False False 16m operator-lifecycle-manager 4.19.9 True False False 31m operator-lifecycle-manager-catalog 4.19.9 True False False 31m operator-lifecycle-manager-packageserver 4.19.9 True False False 31m service-ca 4.19.9 True False False 17m storage 4.19.9 True False False 19m 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 17m csi-snapshot-controller 4.19.9 True False False 32m dns 4.19.9 True False False 17m image-registry 4.19.9 True False False 17m ingress 4.19.9 True False False 15m insights 4.19.9 True False False 18m kube-apiserver 4.19.9 True False False 32m kube-controller-manager 4.19.9 True False False 32m kube-scheduler 4.19.9 True False False 32m kube-storage-version-migrator 4.19.9 True False False 18m monitoring 4.19.9 True False False 2m17s network 4.19.9 True False False 31m node-tuning 4.19.9 True False False 5m1s openshift-apiserver 4.19.9 True False False 32m openshift-controller-manager 4.19.9 True False False 32m openshift-samples 4.19.9 True False False 17m operator-lifecycle-manager 4.19.9 True False False 32m operator-lifecycle-manager-catalog 4.19.9 True False False 32m operator-lifecycle-manager-packageserver 4.19.9 True False False 32m service-ca 4.19.9 True False False 18m storage 4.19.9 True False False 20m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!