INFO: Log in to your Red Hat account... INFO: Configure AWS Credentials... WARN: The current version (1.2.59) is not up to date with latest rosa cli released version (1.2.60). 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.59) is not up to date with latest rosa cli released version (1.2.60). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-db5076d04b' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-db5076d04b' 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-db5076d04b Domain Prefix: kx-db5076d04b Display Name: kx-db5076d04b ID: 2o2b3iveck3tl0oosi83uhupq3bvjpi6 External ID: ed100db4-d4fe-4d7e-84f9-30762c3bff9e Control Plane: ROSA Service Hosted OpenShift Version: 4.19.9 Channel Group: stable DNS: Not ready AWS Account: 381492310364 AWS Billing Account: 381492310364 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-0208a6297964e4fe1, subnet-0c161c939f7025e15, subnet-023e5c7b3016ed194, subnet-02dbd8abbf884d77f, subnet-0360c2d20442c5ba5, subnet-0aad9c992e402a91a EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::381492310364:role/rhads-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cloud-network-config-controller-cloud-creden - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-control-plane-operator - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kms-provider - 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-openshift-image-registry-installer-cloud-credentials Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Jan 26 2026 05:46:58 UTC Details Page: https://console.redhat.com/openshift/details/s/38mYsIo2LffZFAwAxIDpuBTdq9m OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2jtsga3i2etnl697l7bk5i1kmbm4a95j (Managed) Etcd Encryption: Disabled Audit Log Forwarding: Disabled External Authentication: 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-db5076d04b'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-db5076d04b --watch'. INFO: Track the progress of the cluster creation... WARN: The current version (1.2.59) is not up to date with latest rosa cli released version (1.2.60). 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-db5076d04b' 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-db5076d04b Version 2026-01-26 05:56:01 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2026-01-26 05:56:01 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2026-01-26 05:56:04 +0000 UTC hostedclusters kx-db5076d04b ValidAWSIdentityProvider StatusUnknown 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Condition not found in the CVO. 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Condition not found in the CVO. 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Condition not found in the CVO. 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Condition not found in the CVO. 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Condition not found in the CVO. 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Ignition server deployment not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b HostedCluster is supported by operator configuration 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Release image is valid 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Reconciliation active on resource 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is not found 2026-01-26 05:56:06 +0000 UTC hostedclusters kx-db5076d04b configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2026-01-26 05:56:06 +0000 UTC hostedclusters kx-db5076d04b 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-db5076d04b Version 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Reconciliation active on resource 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Release image is valid 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b HostedCluster is supported by operator configuration 2026-01-26 05:56:06 +0000 UTC hostedclusters kx-db5076d04b HostedCluster is at expected version 2026-01-26 05:57:28 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2026-01-26 05:57:29 +0000 UTC hostedclusters kx-db5076d04b Configuration passes validation 2026-01-26 05:57:30 +0000 UTC hostedclusters kx-db5076d04b Required platform credentials are found 2026-01-26 05:57:35 +0000 UTC hostedclusters kx-db5076d04b Reconciliation completed successfully 2026-01-26 05:57:35 +0000 UTC hostedclusters kx-db5076d04b OIDC configuration is valid 2026-01-26 05:57:36 +0000 UTC hostedclusters kx-db5076d04b Configuration passes validation 2026-01-26 05:57:36 +0000 UTC hostedclusters kx-db5076d04b lookup api.kx-db5076d04b.o56v.p3.openshiftapps.com on 172.30.0.10:53: no such host 2026-01-26 05:57:36 +0000 UTC hostedclusters kx-db5076d04b AWS KMS is not configured 2026-01-26 05:57:57 +0000 UTC hostedclusters kx-db5076d04b All is well 2026-01-26 05:57:57 +0000 UTC hostedclusters kx-db5076d04b All is well 2026-01-26 05:58:24 +0000 UTC hostedclusters kx-db5076d04b EtcdAvailable QuorumAvailable 2026-01-26 05:58:59 +0000 UTC hostedclusters kx-db5076d04b Kube APIServer deployment is available 2026-01-26 05:59:17 +0000 UTC hostedclusters kx-db5076d04b Ignition server deployment is available 2026-01-26 05:59:46 +0000 UTC hostedclusters kx-db5076d04b Unable to apply 4.19.9: some cluster operators are not available 2026-01-26 05:59:46 +0000 UTC hostedclusters kx-db5076d04b Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2026-01-26 05:59:46 +0000 UTC hostedclusters kx-db5076d04b ClusterVersionAvailable FromClusterVersion 2026-01-26 05:59:52 +0000 UTC hostedclusters kx-db5076d04b An update is already in progress and the details are in the Progressing condition 2026-01-26 06:00:16 +0000 UTC hostedclusters kx-db5076d04b Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2026-01-26 06:00:29 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is available 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-db5076d04b Version 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Reconciliation active on resource 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b Release image is valid 2026-01-26 05:56:05 +0000 UTC hostedclusters kx-db5076d04b HostedCluster is supported by operator configuration 2026-01-26 05:56:06 +0000 UTC hostedclusters kx-db5076d04b HostedCluster is at expected version 2026-01-26 05:57:28 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2026-01-26 05:57:29 +0000 UTC hostedclusters kx-db5076d04b Configuration passes validation 2026-01-26 05:57:30 +0000 UTC hostedclusters kx-db5076d04b Required platform credentials are found 2026-01-26 05:57:35 +0000 UTC hostedclusters kx-db5076d04b Reconciliation completed successfully 2026-01-26 05:57:35 +0000 UTC hostedclusters kx-db5076d04b OIDC configuration is valid 2026-01-26 05:57:36 +0000 UTC hostedclusters kx-db5076d04b Configuration passes validation 2026-01-26 05:57:36 +0000 UTC hostedclusters kx-db5076d04b AWS KMS is not configured 2026-01-26 05:57:57 +0000 UTC hostedclusters kx-db5076d04b All is well 2026-01-26 05:57:57 +0000 UTC hostedclusters kx-db5076d04b All is well 2026-01-26 05:58:24 +0000 UTC hostedclusters kx-db5076d04b EtcdAvailable QuorumAvailable 2026-01-26 05:58:59 +0000 UTC hostedclusters kx-db5076d04b Kube APIServer deployment is available 2026-01-26 05:59:17 +0000 UTC hostedclusters kx-db5076d04b Ignition server deployment is available 2026-01-26 05:59:46 +0000 UTC hostedclusters kx-db5076d04b ClusterVersionAvailable FromClusterVersion 2026-01-26 05:59:46 +0000 UTC hostedclusters kx-db5076d04b Payload loaded version="4.19.9" image="quay.io/openshift-release-dev/ocp-release@sha256:fda39a9c5701bf35da74263177d8976d4bd9205e69b9a9d5834389f71005d51a" architecture="Multi" 2026-01-26 05:59:46 +0000 UTC hostedclusters kx-db5076d04b Unable to apply 4.19.9: some cluster operators are not available 2026-01-26 05:59:52 +0000 UTC hostedclusters kx-db5076d04b An update is already in progress and the details are in the Progressing condition 2026-01-26 06:00:16 +0000 UTC hostedclusters kx-db5076d04b Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2026-01-26 06:00:35 +0000 UTC hostedclusters kx-db5076d04b The hosted cluster is not degraded 2026-01-26 06:00:36 +0000 UTC hostedclusters kx-db5076d04b All is well 2026-01-26 06:00:38 +0000 UTC hostedclusters kx-db5076d04b All is well 2026-01-26 06:00:52 +0000 UTC hostedclusters kx-db5076d04b The hosted control plane is available INFO: Cluster 'kx-db5076d04b' 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.59) is not up to date with latest rosa cli released version (1.2.60). 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 3m56s dns 4.19.9 False False True 3m58s DNS "default" is unavailable. image-registry False True True 3m44s Available: The deployment does not have available replicas... ingress False True True 3m37s 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 3m49s kube-controller-manager 4.19.9 True False False 3m49s kube-scheduler 4.19.9 True False False 3m49s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m30s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m36s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m49s openshift-controller-manager 4.19.9 True False False 3m49s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m50s operator-lifecycle-manager-catalog 4.19.9 True False False 3m37s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m49s service-ca storage 4.19.9 False False False 3m48s 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 3m56s dns 4.19.9 False False True 3m58s DNS "default" is unavailable. image-registry False True True 3m44s Available: The deployment does not have available replicas... ingress False True True 3m37s 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 3m49s kube-controller-manager 4.19.9 True False False 3m49s kube-scheduler 4.19.9 True False False 3m49s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m30s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m36s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m49s openshift-controller-manager 4.19.9 True False False 3m49s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m50s operator-lifecycle-manager-catalog 4.19.9 True False False 3m37s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m49s service-ca storage 4.19.9 False False False 3m48s 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 4m57s dns 4.19.9 False False True 4m59s DNS "default" is unavailable. image-registry False True True 4m45s Available: The deployment does not have available replicas... ingress False True True 4m38s 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 4m50s kube-controller-manager 4.19.9 True False False 4m50s kube-scheduler 4.19.9 True False False 4m50s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 4m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m50s openshift-controller-manager 4.19.9 True False False 4m50s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m51s operator-lifecycle-manager-catalog 4.19.9 True False False 4m38s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m50s service-ca storage 4.19.9 False False False 4m49s 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 5m57s dns 4.19.9 False False True 5m59s DNS "default" is unavailable. image-registry False True True 5m45s Available: The deployment does not have available replicas... ingress False True True 5m38s 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 5m50s kube-controller-manager 4.19.9 True False False 5m50s kube-scheduler 4.19.9 True False False 5m50s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 5m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m50s openshift-controller-manager 4.19.9 True False False 5m50s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m51s operator-lifecycle-manager-catalog 4.19.9 True False False 5m38s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m50s service-ca storage 4.19.9 False False False 5m49s 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 6m57s dns 4.19.9 False False True 6m59s DNS "default" is unavailable. image-registry False True True 6m45s Available: The deployment does not have available replicas... ingress False True True 6m38s 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 6m50s kube-controller-manager 4.19.9 True False False 6m50s kube-scheduler 4.19.9 True False False 6m50s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 6m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 6m50s openshift-controller-manager 4.19.9 True False False 6m50s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m51s operator-lifecycle-manager-catalog 4.19.9 True False False 6m38s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m50s service-ca storage 4.19.9 False False False 6m49s 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 7m57s dns 4.19.9 False False True 7m59s DNS "default" is unavailable. image-registry False True True 7m45s Available: The deployment does not have available replicas... ingress False True True 7m38s 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 7m50s kube-controller-manager 4.19.9 True False False 7m50s kube-scheduler 4.19.9 True False False 7m50s kube-storage-version-migrator monitoring network 4.19.9 True True False 7m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 7m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 7m50s openshift-controller-manager 4.19.9 True False False 7m50s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m51s operator-lifecycle-manager-catalog 4.19.9 True False False 7m38s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m50s service-ca storage 4.19.9 False False False 7m49s 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 8m58s dns 4.19.9 False False True 9m DNS "default" is unavailable. image-registry False True True 8m46s Available: The deployment does not have available replicas... ingress False True True 8m39s 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 8m51s kube-controller-manager 4.19.9 True False False 8m51s kube-scheduler 4.19.9 True False False 8m51s kube-storage-version-migrator monitoring network 4.19.9 True True False 8m32s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 8m38s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 8m51s openshift-controller-manager 4.19.9 True False False 8m51s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m52s operator-lifecycle-manager-catalog 4.19.9 True False False 8m39s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m51s service-ca storage 4.19.9 False False False 8m50s 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 9m58s dns 4.19.9 False False True 10m DNS "default" is unavailable. image-registry False True True 9m46s Available: The deployment does not have available replicas... ingress False True True 9m39s 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 9m51s kube-controller-manager 4.19.9 True False False 9m51s kube-scheduler 4.19.9 True False False 9m51s kube-storage-version-migrator monitoring network 4.19.9 True True False 9m32s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 9m38s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 9m51s openshift-controller-manager 4.19.9 True False False 9m51s openshift-samples operator-lifecycle-manager 4.19.9 True False False 9m52s operator-lifecycle-manager-catalog 4.19.9 True False False 9m39s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m51s service-ca storage 4.19.9 False False False 9m50s 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 11m 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/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.19.9 True True False 8s 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 5s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 False True False 0s DeploymentAvailable: 0 replicas available for console deployment csi-snapshot-controller 4.19.9 True False False 11m dns 4.19.9 False True True 12m 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 42s kube-apiserver 4.19.9 True False False 11m kube-controller-manager 4.19.9 True False False 11m kube-scheduler 4.19.9 True False False 11m kube-storage-version-migrator 4.19.9 True False False 40s monitoring Unknown True Unknown 17s Rolling out the stack. network 4.19.9 True False False 11m node-tuning 4.19.9 True False False 68s openshift-apiserver 4.19.9 True False False 11m openshift-controller-manager 4.19.9 True False False 11m openshift-samples operator-lifecycle-manager 4.19.9 True False False 11m operator-lifecycle-manager-catalog 4.19.9 True False False 11m operator-lifecycle-manager-packageserver 4.19.9 True False False 11m service-ca 4.19.9 True False False 41s storage 4.19.9 True False False 65s 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 54s 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 57s image-registry True True False 30s Progressing: The deployment has not completed... ingress 4.19.9 True True False 47s 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 102s kube-apiserver 4.19.9 True False False 12m kube-controller-manager 4.19.9 True False False 12m kube-scheduler 4.19.9 True False False 12m kube-storage-version-migrator 4.19.9 True False False 100s monitoring Unknown True Unknown 77s Rolling out the stack. network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 2m8s 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 45s operator-lifecycle-manager 4.19.9 True False False 12m operator-lifecycle-manager-catalog 4.19.9 True False False 12m operator-lifecycle-manager-packageserver 4.19.9 True False False 12m service-ca 4.19.9 True False False 101s storage 4.19.9 True False False 2m5s 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 115s 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 118s image-registry True True True 91s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 108s 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 2m43s kube-apiserver 4.19.9 True False False 13m kube-controller-manager 4.19.9 True False False 13m kube-scheduler 4.19.9 True False False 13m kube-storage-version-migrator 4.19.9 True False False 2m41s monitoring Unknown True Unknown 2m18s Rolling out the stack. network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 3m9s 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 106s operator-lifecycle-manager 4.19.9 True False False 13m operator-lifecycle-manager-catalog 4.19.9 True False False 13m operator-lifecycle-manager-packageserver 4.19.9 True False False 13m service-ca 4.19.9 True False False 2m42s storage 4.19.9 True False False 3m6s 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 2m55s 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 2m58s image-registry True True True 2m31s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 2m48s 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 3m43s kube-apiserver 4.19.9 True False False 14m kube-controller-manager 4.19.9 True False False 14m kube-scheduler 4.19.9 True False False 14m kube-storage-version-migrator 4.19.9 True False False 3m41s monitoring Unknown True Unknown 3m18s Rolling out the stack. network 4.19.9 True True False 14m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 27s Waiting for 2/3 Profiles to be applied 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 2m46s operator-lifecycle-manager 4.19.9 True False False 14m operator-lifecycle-manager-catalog 4.19.9 True False False 14m operator-lifecycle-manager-packageserver 4.19.9 True False False 14m service-ca 4.19.9 True False False 3m42s storage 4.19.9 True False False 4m6s 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 3m55s 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 3m58s image-registry True True True 3m31s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 3m48s 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 4m43s kube-apiserver 4.19.9 True False False 15m kube-controller-manager 4.19.9 True False False 15m kube-scheduler 4.19.9 True False False 15m kube-storage-version-migrator 4.19.9 True False False 4m41s monitoring Unknown True Unknown 4m18s Rolling out the stack. network 4.19.9 True True False 15m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 87s Waiting for 2/3 Profiles to be applied 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 3m46s operator-lifecycle-manager 4.19.9 True False False 15m operator-lifecycle-manager-catalog 4.19.9 True False False 15m operator-lifecycle-manager-packageserver 4.19.9 True False False 15m service-ca 4.19.9 True False False 4m42s storage 4.19.9 True False False 5m6s 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 4m55s 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 4m58s image-registry True True True 4m31s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 4m48s 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 5m43s kube-apiserver 4.19.9 True False False 16m kube-controller-manager 4.19.9 True False False 16m kube-scheduler 4.19.9 True False False 16m kube-storage-version-migrator 4.19.9 True False False 5m41s monitoring Unknown True Unknown 5m18s Rolling out the stack. network 4.19.9 True True False 16m DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 2m27s Waiting for 2/3 Profiles to be applied 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 4m46s operator-lifecycle-manager 4.19.9 True False False 16m operator-lifecycle-manager-catalog 4.19.9 True False False 16m operator-lifecycle-manager-packageserver 4.19.9 True False False 16m service-ca 4.19.9 True False False 5m42s storage 4.19.9 True False False 6m6s 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 5m56s 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 5m59s image-registry True True True 5m32s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 5m49s 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 6m44s kube-apiserver 4.19.9 True False False 17m kube-controller-manager 4.19.9 True False False 17m kube-scheduler 4.19.9 True False False 17m kube-storage-version-migrator 4.19.9 True False False 6m42s monitoring Unknown True Unknown 6m19s Rolling out the stack. network 4.19.9 True True False 17m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 3m28s Waiting for 2/3 Profiles to be applied 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 5m47s operator-lifecycle-manager 4.19.9 True False False 17m operator-lifecycle-manager-catalog 4.19.9 True False False 17m operator-lifecycle-manager-packageserver 4.19.9 True False False 17m service-ca 4.19.9 True False False 6m43s storage 4.19.9 True False False 7m7s 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 6m56s 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 6m59s image-registry True True True 6m32s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 6m49s 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 7m44s 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 7m42s monitoring Unknown True Unknown 7m19s Rolling out the stack. network 4.19.9 True True False 18m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 4m28s Waiting for 2/3 Profiles to be applied 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 6m47s 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 7m43s storage 4.19.9 True False False 8m7s 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 7m56s 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 7m59s image-registry True True True 7m32s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 7m49s 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 8m44s 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 8m42s monitoring Unknown True Unknown 8m19s Rolling out the stack. network 4.19.9 True True False 19m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True True False 5m28s Waiting for 2/3 Profiles to be applied 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 7m47s 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 8m43s storage 4.19.9 True False False 9m7s 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 8m56s 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 8m59s image-registry True True True 8m32s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 8m49s 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 9m44s 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 9m42s monitoring Unknown True Unknown 9m19s Rolling out the stack. network 4.19.9 True True True 20m DaemonSet "/openshift-multus/multus" rollout is not making progress - pod multus-6zhjn is in CrashLoopBackOff State... node-tuning 4.19.9 True False False 6m28s 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 8m47s 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 9m43s 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 9m56s 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 True True 9m59s DNS default is degraded image-registry True True True 9m32s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-797f7f9456" has timed out progressing. ingress 4.19.9 True True False 9m49s 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 True False 21m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes) node-tuning 4.19.9 True False False 7m28s 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 9m47s 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 23m dns 4.19.9 True False False 11m 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 8m29s 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 True False 11m 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 12m 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 21s network 4.19.9 True False False 23m node-tuning 4.19.9 True False False 9m30s 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 25m dns 4.19.9 True False False 13m 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 81s network 4.19.9 True False False 24m node-tuning 4.19.9 True False False 10m 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 26m dns 4.19.9 True False False 14m 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 2m21s network 4.19.9 True False False 25m node-tuning 4.19.9 True False False 11m 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 27m dns 4.19.9 True False False 15m 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 3m21s network 4.19.9 True False False 26m node-tuning 4.19.9 True False False 12m 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 28m dns 4.19.9 True False False 16m 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 4m22s network 4.19.9 True False False 27m node-tuning 4.19.9 True False False 13m 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 NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True False False 16m csi-snapshot-controller 4.19.9 True False False 29m dns 4.19.9 True False False 17m image-registry 4.19.9 True False False 16m ingress 4.19.9 True True False 16m 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 17m 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 17m monitoring 4.19.9 True False False 5m22s network 4.19.9 True False False 28m node-tuning 4.19.9 True False False 14m 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 16m 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 17m 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 17m csi-snapshot-controller 4.19.9 True False False 30m dns 4.19.9 True False False 18m image-registry 4.19.9 True False False 17m ingress 4.19.9 True True False 17m 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 18m 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 18m monitoring 4.19.9 True False False 6m22s network 4.19.9 True False False 29m node-tuning 4.19.9 True False False 15m 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 17m 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 18m storage 4.19.9 True False False 19m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!