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-b9a60055de' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-b9a60055de' 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-b9a60055de Domain Prefix: kx-b9a60055de Display Name: kx-b9a60055de ID: 2m3pn5ehgh10e8frb4ul7pvheacqngi8 External ID: 166127b6-26d2-4be4-a816-46455591c7d3 Control Plane: ROSA Service Hosted OpenShift Version: 4.19.9 Channel Group: stable DNS: Not ready AWS Account: 381492310364 AWS Billing Account: 381492310364 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-0208a6297964e4fe1, subnet-0c161c939f7025e15, subnet-023e5c7b3016ed194, subnet-02dbd8abbf884d77f, subnet-0360c2d20442c5ba5, subnet-0aad9c992e402a91a EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::381492310364:role/rhads-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cloud-network-config-controller-cloud-creden - arn:aws:iam::381492310364:role/rhads-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kube-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-capa-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-control-plane-operator - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kms-provider Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 23 2025 08:38:51 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34SZ3AHC47ASzS0o7GsMVcwLlxd 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-b9a60055de'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-b9a60055de --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-b9a60055de' 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-b9a60055de Version 2025-10-23 08:42:56 +0000 UTC hostedclusters kx-b9a60055de ValidAWSIdentityProvider StatusUnknown 2025-10-23 08:42:57 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-23 08:42:57 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Ignition server deployment not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de HostedCluster is supported by operator configuration 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Release image is valid 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Reconciliation active on resource 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is not found 2025-10-23 08:43:05 +0000 UTC hostedclusters kx-b9a60055de configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-23 08:43:05 +0000 UTC hostedclusters kx-b9a60055de 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-b9a60055de Version 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Release image is valid 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Waiting for hosted control plane kubeconfig to be created 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Reconciliation active on resource 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de HostedCluster is supported by operator configuration 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Ignition server deployment not found 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Condition not found in the CVO. 2025-10-23 08:43:05 +0000 UTC hostedclusters kx-b9a60055de HostedCluster is at expected version 2025-10-23 08:44:25 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-23 08:44:40 +0000 UTC hostedclusters kx-b9a60055de Configuration passes validation 2025-10-23 08:44:42 +0000 UTC hostedclusters kx-b9a60055de Required platform credentials are found 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de AWS KMS is not configured 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de capi-provider deployment has 2 unavailable replicas 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de lookup api.kx-b9a60055de.a58i.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de Configuration passes validation 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de Kube APIServer deployment not found 2025-10-23 08:44:46 +0000 UTC hostedclusters kx-b9a60055de OIDC configuration is valid 2025-10-23 08:44:46 +0000 UTC hostedclusters kx-b9a60055de Reconciliation completed successfully 2025-10-23 08:45:07 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:45:07 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:45:14 +0000 UTC hostedclusters kx-b9a60055de WebIdentityErr 2025-10-23 08:45:36 +0000 UTC hostedclusters kx-b9a60055de EtcdAvailable QuorumAvailable 2025-10-23 08:46:20 +0000 UTC hostedclusters kx-b9a60055de Kube APIServer deployment is available 2025-10-23 08:46:38 +0000 UTC hostedclusters kx-b9a60055de [catalog-operator deployment has 1 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, olm-operator deployment has 1 unavailable replicas, router deployment has 2 unavailable replicas] 2025-10-23 08:46:44 +0000 UTC hostedclusters kx-b9a60055de Ignition server deployment is available 2025-10-23 08:46:44 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:46:47 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:46:50 +0000 UTC hostedclusters kx-b9a60055de Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-23 08:46:50 +0000 UTC hostedclusters kx-b9a60055de ClusterVersionAvailable FromClusterVersion 2025-10-23 08:46:50 +0000 UTC hostedclusters kx-b9a60055de Unable to apply 4.19.9: an unknown error has occurred: MultipleErrors 2025-10-23 08:46:57 +0000 UTC hostedclusters kx-b9a60055de An update is already in progress and the details are in the Progressing condition 2025-10-23 08:47:21 +0000 UTC hostedclusters kx-b9a60055de Multiple errors are preventing progress: * Cluster operators dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, network, node-tuning, openshift-samples, service-ca are not available * Could not update imagestream "openshift/driver-toolkit" (447 of 629): resource may have been deleted * Could not update oauthclient "console" (378 of 629): the server does not recognize this resource, check extension API servers * Could not update operatorgroup "openshift-monitoring/openshift-cluster-monitoring" (570 of 629): resource may have been deleted * Could not update role "openshift-authentication/prometheus-k8s" (557 of 629): resource may have been deleted * Could not update role "openshift-console-operator/prometheus-k8s" (587 of 629): resource may have been deleted * Could not update role "openshift-console/prometheus-k8s" (591 of 629): resource may have been deleted * Could not update role "openshift-ingress-operator/prometheus-k8s" (598 of 629): resource may have been deleted * Could not update role "openshift-kube-apiserver-operator/prometheus-k8s" (602 of 629): resource may have been deleted 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-b9a60055de Version 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Reconciliation active on resource 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de Release image is valid 2025-10-23 08:43:02 +0000 UTC hostedclusters kx-b9a60055de HostedCluster is supported by operator configuration 2025-10-23 08:43:05 +0000 UTC hostedclusters kx-b9a60055de HostedCluster is at expected version 2025-10-23 08:44:25 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-23 08:44:40 +0000 UTC hostedclusters kx-b9a60055de Configuration passes validation 2025-10-23 08:44:42 +0000 UTC hostedclusters kx-b9a60055de Required platform credentials are found 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de Configuration passes validation 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de lookup api.kx-b9a60055de.a58i.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-23 08:44:45 +0000 UTC hostedclusters kx-b9a60055de AWS KMS is not configured 2025-10-23 08:44:46 +0000 UTC hostedclusters kx-b9a60055de Reconciliation completed successfully 2025-10-23 08:44:46 +0000 UTC hostedclusters kx-b9a60055de OIDC configuration is valid 2025-10-23 08:45:07 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:45:07 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:45:36 +0000 UTC hostedclusters kx-b9a60055de EtcdAvailable QuorumAvailable 2025-10-23 08:46:20 +0000 UTC hostedclusters kx-b9a60055de Kube APIServer deployment is available 2025-10-23 08:46:44 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:46:44 +0000 UTC hostedclusters kx-b9a60055de Ignition server deployment is available 2025-10-23 08:46:47 +0000 UTC hostedclusters kx-b9a60055de All is well 2025-10-23 08:46:50 +0000 UTC hostedclusters kx-b9a60055de Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2025-10-23 08:46:50 +0000 UTC hostedclusters kx-b9a60055de ClusterVersionAvailable FromClusterVersion 2025-10-23 08:46:50 +0000 UTC hostedclusters kx-b9a60055de Unable to apply 4.19.9: some cluster operators are not available 2025-10-23 08:46:57 +0000 UTC hostedclusters kx-b9a60055de An update is already in progress and the details are in the Progressing condition 2025-10-23 08:47:21 +0000 UTC hostedclusters kx-b9a60055de Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-10-23 08:47:41 +0000 UTC hostedclusters kx-b9a60055de The hosted control plane is available INFO: Cluster 'kx-b9a60055de' 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 3m37s dns 4.19.9 False False True 3m36s DNS "default" is unavailable. image-registry False True True 3m19s Available: The deployment does not have available replicas... ingress False True True 3m16s 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 3m24s kube-controller-manager 4.19.9 True False False 3m24s kube-scheduler 4.19.9 True False False 3m24s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m10s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m3s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m24s openshift-controller-manager 4.19.9 True False False 3m24s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m26s operator-lifecycle-manager-catalog 4.19.9 True False False 3m27s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m24s service-ca storage 4.19.9 False False False 3m23s 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 3m38s dns 4.19.9 False False True 3m37s DNS "default" is unavailable. image-registry False True True 3m20s Available: The deployment does not have available replicas... ingress False True True 3m17s 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 3m25s kube-controller-manager 4.19.9 True False False 3m25s kube-scheduler 4.19.9 True False False 3m25s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m11s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m25s openshift-controller-manager 4.19.9 True False False 3m25s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m27s operator-lifecycle-manager-catalog 4.19.9 True False False 3m28s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m25s service-ca storage 4.19.9 False False False 3m24s 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 4m38s dns 4.19.9 False False True 4m37s DNS "default" is unavailable. image-registry False True True 4m20s 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.19.9 True False False 4m25s kube-controller-manager 4.19.9 True False False 4m25s kube-scheduler 4.19.9 True False False 4m25s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m11s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m25s openshift-controller-manager 4.19.9 True False False 4m25s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m27s operator-lifecycle-manager-catalog 4.19.9 True False False 4m28s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m25s service-ca storage 4.19.9 False False False 4m24s 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 5m38s dns 4.19.9 False False True 5m37s DNS "default" is unavailable. image-registry False True True 5m20s Available: The deployment does not have available replicas... ingress False True True 5m17s 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 5m25s kube-controller-manager 4.19.9 True False False 5m25s kube-scheduler 4.19.9 True False False 5m25s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m11s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 5m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m25s openshift-controller-manager 4.19.9 True False False 5m25s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m27s operator-lifecycle-manager-catalog 4.19.9 True False False 5m28s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m25s service-ca storage 4.19.9 False False False 5m24s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s Unable to connect to the server: dial tcp: lookup api.kx-b9a60055de.a58i.p3.openshiftapps.com on 172.30.0.10:53: no such host 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 7m39s dns 4.19.9 False False True 7m38s DNS "default" is unavailable. image-registry False True True 7m21s 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.19.9 True False False 7m26s kube-controller-manager 4.19.9 True False False 7m26s kube-scheduler 4.19.9 True False False 7m26s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m12s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 7m5s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 7m26s openshift-controller-manager 4.19.9 True False False 7m26s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m28s operator-lifecycle-manager-catalog 4.19.9 True False False 7m29s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m26s service-ca storage 4.19.9 False False False 7m25s 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 8m39s dns 4.19.9 False False True 8m38s DNS "default" is unavailable. image-registry False True True 8m21s 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 kube-apiserver 4.19.9 True False False 8m26s kube-controller-manager 4.19.9 True False False 8m26s kube-scheduler 4.19.9 True False False 8m26s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m12s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 8m5s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 8m26s openshift-controller-manager 4.19.9 True False False 8m26s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m28s operator-lifecycle-manager-catalog 4.19.9 True False False 8m29s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m26s service-ca storage 4.19.9 False False False 8m25s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s Unable to connect to the server: dial tcp: lookup api.kx-b9a60055de.a58i.p3.openshiftapps.com on 172.30.0.10:53: no such host Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 10m dns 4.19.9 False False True 10m DNS "default" is unavailable. image-registry False True True 10m Available: The deployment does not have available replicas... ingress False True True 10m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 10m kube-controller-manager 4.19.9 True False False 10m kube-scheduler 4.19.9 True False False 10m kube-storage-version-migrator monitoring network 4.19.9 True True False 10m DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 27s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.19.9 True False False 10m openshift-controller-manager 4.19.9 True False False 10m openshift-samples operator-lifecycle-manager 4.19.9 True False False 10m operator-lifecycle-manager-catalog 4.19.9 True False False 10m operator-lifecycle-manager-packageserver 4.19.9 True False False 10m service-ca storage 4.19.9 True False False 13s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 Unknown False False 16s csi-snapshot-controller 4.19.9 True False False 11m dns 4.19.9 False True True 11m DNS "default" is unavailable. image-registry False True True 11m Available: The deployment does not have available replicas... ingress False True True 11m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.19.9 True False False 33s kube-apiserver 4.19.9 True False False 11m kube-controller-manager 4.19.9 True False False 11m kube-scheduler 4.19.9 True False False 11m kube-storage-version-migrator 4.19.9 True False False 29s monitoring Unknown True Unknown 5s Rolling out the stack. network 4.19.9 True True False 11m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.19.9 True False False 88s openshift-apiserver 4.19.9 True False False 11m openshift-controller-manager 4.19.9 True False False 11m openshift-samples operator-lifecycle-manager 4.19.9 True False False 11m operator-lifecycle-manager-catalog 4.19.9 True False False 11m operator-lifecycle-manager-packageserver 4.19.9 True False False 11m service-ca 4.19.9 True False False 30s storage 4.19.9 True False False 74s 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 44s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 12m dns 4.19.9 True False False 35s image-registry True True False 35s Progressing: The deployment has not completed... ingress 4.19.9 True True False 34s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 93s kube-apiserver 4.19.9 True False False 12m kube-controller-manager 4.19.9 True False False 12m kube-scheduler 4.19.9 True False False 12m kube-storage-version-migrator 4.19.9 True False False 89s monitoring Unknown True Unknown 65s Rolling out the stack. network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 2m28s openshift-apiserver 4.19.9 True False False 12m openshift-controller-manager 4.19.9 True False False 12m openshift-samples 4.19.9 True False False 28s operator-lifecycle-manager 4.19.9 True False False 12m operator-lifecycle-manager-catalog 4.19.9 True False False 12m operator-lifecycle-manager-packageserver 4.19.9 True False False 12m service-ca 4.19.9 True False False 90s storage 4.19.9 True False False 2m14s 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 104s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 13m dns 4.19.9 True False False 95s image-registry True True True 95s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 94s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 2m33s kube-apiserver 4.19.9 True False False 13m kube-controller-manager 4.19.9 True False False 13m kube-scheduler 4.19.9 True False False 13m kube-storage-version-migrator 4.19.9 True False False 2m29s monitoring Unknown True Unknown 2m5s Rolling out the stack. network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 3m28s openshift-apiserver 4.19.9 True False False 13m openshift-controller-manager 4.19.9 True False False 13m openshift-samples 4.19.9 True False False 88s operator-lifecycle-manager 4.19.9 True False False 13m operator-lifecycle-manager-catalog 4.19.9 True False False 13m operator-lifecycle-manager-packageserver 4.19.9 True False False 13m service-ca 4.19.9 True False False 2m30s storage 4.19.9 True False False 3m14s 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 2m44s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 14m dns 4.19.9 True False False 2m35s image-registry True True True 2m35s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 2m34s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 3m33s 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 3m29s monitoring Unknown True Unknown 3m5s Rolling out the stack. network 4.19.9 True False False 14m node-tuning 4.19.9 True False False 4m28s openshift-apiserver 4.19.9 True False False 14m openshift-controller-manager 4.19.9 True False False 14m openshift-samples 4.19.9 True False False 2m28s 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 3m30s storage 4.19.9 True False False 4m14s 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 3m45s 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 3m36s image-registry True True True 3m36s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 3m35s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 4m34s 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 4m30s monitoring Unknown True Unknown 4m6s Rolling out the stack. network 4.19.9 True False False 15m node-tuning 4.19.9 True False False 5m29s 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 3m29s 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 4m31s storage 4.19.9 True False False 5m15s 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 4m45s 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 4m36s image-registry True True True 4m36s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 4m35s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 5m34s 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 5m30s monitoring Unknown True Unknown 5m6s Rolling out the stack. network 4.19.9 True False False 16m node-tuning 4.19.9 True False False 6m29s 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 4m29s 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 5m31s storage 4.19.9 True False False 6m15s 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 5m45s 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 5m36s image-registry True True True 5m36s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 5m35s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 6m34s 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 6m30s monitoring Unknown True Unknown 6m6s Rolling out the stack. network 4.19.9 True False False 17m node-tuning 4.19.9 True False False 7m29s 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 5m29s 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 6m31s storage 4.19.9 True False False 7m15s 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 6m45s 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 6m36s image-registry True True True 6m36s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 6m35s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 7m34s 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 7m30s monitoring Unknown True Unknown 7m6s Rolling out the stack. network 4.19.9 True False False 18m node-tuning 4.19.9 True False False 8m29s 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 6m29s 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 7m31s storage 4.19.9 True False False 8m15s 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 7m46s 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 7m37s image-registry True True True 7m37s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 7m36s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 8m35s 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 8m31s monitoring Unknown True Unknown 8m7s Rolling out the stack. network 4.19.9 True False False 19m node-tuning 4.19.9 True False False 9m30s 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 7m30s 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 8m32s storage 4.19.9 True False False 9m16s 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 8m46s 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 True False 8m37s DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 3." image-registry True True True 8m37s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-69cf476f88" has timed out progressing. ingress 4.19.9 True True False 8m36s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 9m35s 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 9m31s monitoring Unknown True Unknown 9m7s Rolling out the stack. network 4.19.9 True True False 20m DaemonSet "/openshift-multus/multus" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 15s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.19.9 True False False 20m openshift-controller-manager 4.19.9 True False False 20m openshift-samples 4.19.9 True False False 8m30s 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 9m32s storage 4.19.9 True True False 10m AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 9m46s 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 9m37s image-registry 4.19.9 True False False 9m37s ingress 4.19.9 True True False 9m36s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 10m 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 10m monitoring Unknown True Unknown 10m Rolling out the stack. network 4.19.9 True False False 21m node-tuning 4.19.9 True False False 75s 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 9m30s 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 10m 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 False False 10m csi-snapshot-controller 4.19.9 True False False 22m dns 4.19.9 True False False 10m image-registry 4.19.9 True False False 10m 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 old replica(s) are pending termination...... insights 4.19.9 True False False 11m 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 11m monitoring Unknown True Unknown 11m Rolling out the stack. network 4.19.9 True False False 22m node-tuning 4.19.9 True False False 2m16s 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 10m 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 11m 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 False False 11m csi-snapshot-controller 4.19.9 True False False 23m dns 4.19.9 True False False 11m image-registry 4.19.9 True False False 11m 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 old replica(s) are pending termination...... insights 4.19.9 True False False 12m 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 12m monitoring 4.19.9 True False False 32s network 4.19.9 True False False 23m node-tuning 4.19.9 True False False 3m16s 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 11m 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 12m 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 False False 12m csi-snapshot-controller 4.19.9 True False False 24m dns 4.19.9 True False False 12m image-registry 4.19.9 True False False 12m ingress 4.19.9 True True False 12m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 13m 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 13m monitoring 4.19.9 True False False 92s network 4.19.9 True False False 24m node-tuning 4.19.9 True False False 4m16s 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 12m 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 13m 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 False False 13m csi-snapshot-controller 4.19.9 True False False 25m dns 4.19.9 True False False 13m image-registry 4.19.9 True False False 13m ingress 4.19.9 True True False 13m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 14m 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 14m monitoring 4.19.9 True False False 2m32s network 4.19.9 True False False 25m node-tuning 4.19.9 True False False 5m16s 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 13m 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 14m storage 4.19.9 True False False 15m 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 26m dns 4.19.9 True False False 14m image-registry 4.19.9 True False False 14m ingress 4.19.9 True True False 14m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 15m 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 15m monitoring 4.19.9 True False False 3m33s network 4.19.9 True False False 26m node-tuning 4.19.9 True False False 6m17s 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 14m 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 15m 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 15m csi-snapshot-controller 4.19.9 True False False 27m dns 4.19.9 True False False 15m image-registry 4.19.9 True False False 15m ingress 4.19.9 True True False 15m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.19.9 True False False 16m 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 16m monitoring 4.19.9 True False False 4m33s network 4.19.9 True False False 27m node-tuning 4.19.9 True False False 7m17s 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 15m 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 16m storage 4.19.9 True False False 17m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!