INFO: Log in to your Red Hat account... INFO: Configure AWS Credentials... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com' INFO: Create ROSA with HCP cluster... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-d4052ded4e' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-d4052ded4e' 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-d4052ded4e Domain Prefix: kx-d4052ded4e Display Name: kx-d4052ded4e ID: 2m541696nd3ldmuiguf4b12eajsjkluq External ID: 862a5e33-4424-4cf9-ab19-7e29fc03573e Control Plane: ROSA Service Hosted OpenShift Version: 4.17.41 Channel Group: stable DNS: Not ready AWS Account: 418295695583 AWS Billing Account: 418295695583 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-001fc23497e4a3aeb, subnet-00ffba09365a434bc, subnet-074cbf0329958194a, subnet-0689cd077699b690a, subnet-0f9f09e46f74cde64, subnet-033f48892ddbaa09d EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 25 2025 08:47:25 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34YEKv5PHN0s1DfWD0d0CvfATy6 OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed) Etcd Encryption: Disabled Audit Log Forwarding: Disabled External Authentication: Disabled Zero Egress: Disabled INFO: Preparing to create operator roles. INFO: Operator Roles already exists INFO: Preparing to create OIDC Provider. INFO: OIDC provider already exists INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-d4052ded4e'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-d4052ded4e --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-d4052ded4e' 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-d4052ded4e Version 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is not found 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e ValidAWSIdentityProvider StatusUnknown 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e HostedCluster is supported by operator configuration 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Release image is valid 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Ignition server deployment not found 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Reconciliation active on resource 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-25 08:51:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-d4052ded4e Version 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Waiting for hosted control plane kubeconfig to be created 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Release image is valid 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e HostedCluster is at expected version 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Reconciliation active on resource 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e HostedCluster is supported by operator configuration 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Ignition server deployment not found 2025-10-25 08:52:37 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-25 08:52:41 +0000 UTC hostedclusters kx-d4052ded4e Configuration passes validation 2025-10-25 08:52:42 +0000 UTC hostedclusters kx-d4052ded4e Required platform credentials are found 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e Kube APIServer deployment not found 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e capi-provider deployment has 2 unavailable replicas 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e AWS KMS is not configured 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e Waiting for etcd to reach quorum 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e Configuration passes validation 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e lookup api.kx-d4052ded4e.5sdv.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-25 08:52:54 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:52:55 +0000 UTC hostedclusters kx-d4052ded4e OIDC configuration is valid 2025-10-25 08:52:55 +0000 UTC hostedclusters kx-d4052ded4e Reconciliation completed successfully 2025-10-25 08:53:09 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:53:14 +0000 UTC hostedclusters kx-d4052ded4e WebIdentityErr 2025-10-25 08:53:30 +0000 UTC hostedclusters kx-d4052ded4e EtcdAvailable QuorumAvailable 2025-10-25 08:53:58 +0000 UTC hostedclusters kx-d4052ded4e Kube APIServer deployment is available 2025-10-25 08:54:14 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:54:18 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:54:22 +0000 UTC hostedclusters kx-d4052ded4e Ignition server deployment is available 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e ClusterVersionSucceeding FromClusterVersion 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e Payload loaded version="4.17.41" image="quay.io/openshift-release-dev/ocp-release@sha256:57f09f90de7ab876109581cef6b2cf9da8ff62818bd9fb1503c0cc26d5a5d80a" architecture="Multi" 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e ClusterVersionAvailable FromClusterVersion 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e Working towards 4.17.41: 362 of 621 done (58% complete) 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-d4052ded4e Version 2025-10-25 08:51:10 +0000 UTC hostedclusters kx-d4052ded4e Get "https://af489aa29928542f4acc289a16a1ee1c-ce1ec868f71c9a62.elb.us-east-1.amazonaws.com:443/healthz": dial tcp: lookup af489aa29928542f4acc289a16a1ee1c-ce1ec868f71c9a62.elb.us-east-1.amazonaws.com on 172.30.0.10:53: no such host 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e HostedCluster is at expected version 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Reconciliation active on resource 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e Release image is valid 2025-10-25 08:51:11 +0000 UTC hostedclusters kx-d4052ded4e HostedCluster is supported by operator configuration 2025-10-25 08:52:37 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-25 08:52:41 +0000 UTC hostedclusters kx-d4052ded4e Configuration passes validation 2025-10-25 08:52:42 +0000 UTC hostedclusters kx-d4052ded4e Required platform credentials are found 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e Configuration passes validation 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e router deployment has 1 unavailable replicas 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e AWS KMS is not configured 2025-10-25 08:52:45 +0000 UTC hostedclusters kx-d4052ded4e lookup api.kx-d4052ded4e.5sdv.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-25 08:52:54 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:52:55 +0000 UTC hostedclusters kx-d4052ded4e OIDC configuration is valid 2025-10-25 08:52:55 +0000 UTC hostedclusters kx-d4052ded4e Reconciliation completed successfully 2025-10-25 08:53:09 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:53:30 +0000 UTC hostedclusters kx-d4052ded4e EtcdAvailable QuorumAvailable 2025-10-25 08:53:58 +0000 UTC hostedclusters kx-d4052ded4e Kube APIServer deployment is available 2025-10-25 08:54:14 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:54:18 +0000 UTC hostedclusters kx-d4052ded4e All is well 2025-10-25 08:54:22 +0000 UTC hostedclusters kx-d4052ded4e Ignition server deployment is available 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e Condition not found in the CVO. 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e Payload loaded version="4.17.41" image="quay.io/openshift-release-dev/ocp-release@sha256:57f09f90de7ab876109581cef6b2cf9da8ff62818bd9fb1503c0cc26d5a5d80a" architecture="Multi" 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e ClusterVersionAvailable FromClusterVersion 2025-10-25 08:54:29 +0000 UTC hostedclusters kx-d4052ded4e Unable to apply 4.17.41: some cluster operators are not available 2025-10-25 08:55:06 +0000 UTC hostedclusters kx-d4052ded4e 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-25 08:55:35 +0000 UTC hostedclusters kx-d4052ded4e The hosted cluster is not degraded 2025-10-25 08:55:42 +0000 UTC hostedclusters kx-d4052ded4e The hosted control plane is available INFO: Cluster 'kx-d4052ded4e' is now ready INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Storing login command... INFO: Check if it's able to login to OCP cluster... Retried 1 times... INFO: Check if apiserver is ready... Waiting for cluster operators to be accessible for 2m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 4m18s dns 4.17.41 False False True 4m19s DNS "default" is unavailable. image-registry False True True 3m26s Available: The deployment does not have available replicas... ingress False True True 4m3s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 4m9s kube-controller-manager 4.17.41 True False False 4m9s kube-scheduler 4.17.41 True False False 4m9s kube-storage-version-migrator monitoring network 4.17.41 True True False 3m56s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m2s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 4m9s openshift-controller-manager 4.17.41 True False False 4m9s openshift-samples operator-lifecycle-manager 4.17.41 True False False 4m12s operator-lifecycle-manager-catalog 4.17.41 True False False 4m3s operator-lifecycle-manager-packageserver 4.17.41 True False False 4m9s service-ca storage 4.17.41 False False False 4m9s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service cluster operators to be accessible finished! [INFO] Cluster operators are accessible. Waiting for cluster to be reported as healthy for 60m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 4m19s dns 4.17.41 False False True 4m20s DNS "default" is unavailable. image-registry False True True 3m27s Available: The deployment does not have available replicas... ingress False True True 4m4s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 4m10s kube-controller-manager 4.17.41 True False False 4m10s kube-scheduler 4.17.41 True False False 4m10s kube-storage-version-migrator monitoring network 4.17.41 True True False 3m57s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m3s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 4m10s openshift-controller-manager 4.17.41 True False False 4m10s openshift-samples operator-lifecycle-manager 4.17.41 True False False 4m13s operator-lifecycle-manager-catalog 4.17.41 True False False 4m4s operator-lifecycle-manager-packageserver 4.17.41 True False False 4m10s service-ca storage 4.17.41 False False False 4m10s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 5m19s dns 4.17.41 False False True 5m20s DNS "default" is unavailable. image-registry False True True 4m27s Available: The deployment does not have available replicas... ingress False True True 5m4s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 5m10s kube-controller-manager 4.17.41 True False False 5m10s kube-scheduler 4.17.41 True False False 5m10s kube-storage-version-migrator monitoring network 4.17.41 True True False 4m57s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 5m3s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 5m10s openshift-controller-manager 4.17.41 True False False 5m10s openshift-samples operator-lifecycle-manager 4.17.41 True False False 5m13s operator-lifecycle-manager-catalog 4.17.41 True False False 5m4s operator-lifecycle-manager-packageserver 4.17.41 True False False 5m10s service-ca storage 4.17.41 False False False 5m10s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 6m20s dns 4.17.41 False False True 6m21s DNS "default" is unavailable. image-registry False True True 5m28s Available: The deployment does not have available replicas... ingress False True True 6m5s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 6m11s kube-controller-manager 4.17.41 True False False 6m11s kube-scheduler 4.17.41 True False False 6m11s kube-storage-version-migrator monitoring network 4.17.41 True True False 5m58s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 6m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 6m11s openshift-controller-manager 4.17.41 True False False 6m11s openshift-samples operator-lifecycle-manager 4.17.41 True False False 6m14s operator-lifecycle-manager-catalog 4.17.41 True False False 6m5s operator-lifecycle-manager-packageserver 4.17.41 True False False 6m11s service-ca storage 4.17.41 False False False 6m11s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 7m20s dns 4.17.41 False False True 7m21s DNS "default" is unavailable. image-registry False True True 6m28s Available: The deployment does not have available replicas... ingress False True True 7m5s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 7m11s kube-controller-manager 4.17.41 True False False 7m11s kube-scheduler 4.17.41 True False False 7m11s kube-storage-version-migrator monitoring network 4.17.41 True True False 6m58s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 7m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 7m11s openshift-controller-manager 4.17.41 True False False 7m11s openshift-samples operator-lifecycle-manager 4.17.41 True False False 7m14s operator-lifecycle-manager-catalog 4.17.41 True False False 7m5s operator-lifecycle-manager-packageserver 4.17.41 True False False 7m11s service-ca storage 4.17.41 False False False 7m11s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 8m20s dns 4.17.41 False False True 8m21s DNS "default" is unavailable. image-registry False True True 7m28s Available: The deployment does not have available replicas... ingress False True True 8m5s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 8m11s kube-controller-manager 4.17.41 True False False 8m11s kube-scheduler 4.17.41 True False False 8m11s kube-storage-version-migrator monitoring network 4.17.41 True True False 7m58s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 8m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 8m11s openshift-controller-manager 4.17.41 True False False 8m11s openshift-samples operator-lifecycle-manager 4.17.41 True False False 8m14s operator-lifecycle-manager-catalog 4.17.41 True False False 8m5s operator-lifecycle-manager-packageserver 4.17.41 True False False 8m11s service-ca storage 4.17.41 False False False 8m11s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 9m20s dns 4.17.41 False False True 9m21s DNS "default" is unavailable. image-registry False True True 8m28s Available: The deployment does not have available replicas... ingress False True True 9m5s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.41 True False False 9m11s kube-controller-manager 4.17.41 True False False 9m11s kube-scheduler 4.17.41 True False False 9m11s kube-storage-version-migrator monitoring network 4.17.41 True True False 8m58s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 9m4s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.41 True False False 9m11s openshift-controller-manager 4.17.41 True False False 9m11s openshift-samples operator-lifecycle-manager 4.17.41 True False False 9m14s operator-lifecycle-manager-catalog 4.17.41 True False False 9m5s operator-lifecycle-manager-packageserver 4.17.41 True False False 9m11s service-ca storage 4.17.41 False False False 9m11s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.41 True False False 10m dns 4.17.41 False False True 10m DNS "default" is unavailable. image-registry False True True 9m29s 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 4.17.41 True False False 8s kube-apiserver 4.17.41 True False False 10m kube-controller-manager 4.17.41 True False False 10m kube-scheduler 4.17.41 True False False 10m kube-storage-version-migrator 4.17.41 True False False 3s monitoring network 4.17.41 True True False 9m59s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)... node-tuning 4.17.41 True False False 41s openshift-apiserver 4.17.41 True False False 10m openshift-controller-manager 4.17.41 True False False 10m openshift-samples operator-lifecycle-manager 4.17.41 True False False 10m operator-lifecycle-manager-catalog 4.17.41 True False False 10m operator-lifecycle-manager-packageserver 4.17.41 True False False 10m service-ca 4.17.41 True False False 6s storage 4.17.41 True False False 38s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 False True False 0s DeploymentAvailable: 0 replicas available for console deployment csi-snapshot-controller 4.17.41 True False False 11m dns 4.17.41 True False False 34s image-registry True True False 28s Progressing: The deployment has not completed... ingress 4.17.41 True True True 10s The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller) insights 4.17.41 True False False 68s kube-apiserver 4.17.41 True False False 11m kube-controller-manager 4.17.41 True False False 11m kube-scheduler 4.17.41 True False False 11m kube-storage-version-migrator 4.17.41 True False False 63s monitoring Unknown True Unknown 39s Rolling out the stack. network 4.17.41 True False False 10m node-tuning 4.17.41 True False False 101s openshift-apiserver 4.17.41 True False False 11m openshift-controller-manager 4.17.41 True False False 11m openshift-samples 4.17.41 True False False 22s operator-lifecycle-manager 4.17.41 True False False 11m operator-lifecycle-manager-catalog 4.17.41 True False False 11m operator-lifecycle-manager-packageserver 4.17.41 True False False 11m service-ca 4.17.41 True False False 66s storage 4.17.41 True False False 98s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 57s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 12m dns 4.17.41 True False False 94s image-registry True True True 88s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 70s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 2m8s kube-apiserver 4.17.41 True False False 12m kube-controller-manager 4.17.41 True False False 12m kube-scheduler 4.17.41 True False False 12m kube-storage-version-migrator 4.17.41 True False False 2m3s monitoring Unknown True Unknown 99s Rolling out the stack. network 4.17.41 True False False 11m node-tuning 4.17.41 True False False 2m41s openshift-apiserver 4.17.41 True False False 12m openshift-controller-manager 4.17.41 True False False 12m openshift-samples 4.17.41 True False False 82s operator-lifecycle-manager 4.17.41 True False False 12m operator-lifecycle-manager-catalog 4.17.41 True False False 12m operator-lifecycle-manager-packageserver 4.17.41 True False False 12m service-ca 4.17.41 True False False 2m6s storage 4.17.41 True False False 2m38s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 117s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 13m dns 4.17.41 True False False 2m34s image-registry True True True 2m28s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 2m10s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 3m8s kube-apiserver 4.17.41 True False False 13m kube-controller-manager 4.17.41 True False False 13m kube-scheduler 4.17.41 True False False 13m kube-storage-version-migrator 4.17.41 True False False 3m3s monitoring Unknown True Unknown 2m39s Rolling out the stack. network 4.17.41 True False False 12m node-tuning 4.17.41 True False False 3m41s openshift-apiserver 4.17.41 True False False 13m openshift-controller-manager 4.17.41 True False False 13m openshift-samples 4.17.41 True False False 2m22s operator-lifecycle-manager 4.17.41 True False False 13m operator-lifecycle-manager-catalog 4.17.41 True False False 13m operator-lifecycle-manager-packageserver 4.17.41 True False False 13m service-ca 4.17.41 True False False 3m6s storage 4.17.41 True False False 3m38s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 2m58s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 14m dns 4.17.41 True False False 3m35s image-registry True True True 3m29s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 3m11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 4m9s kube-apiserver 4.17.41 True False False 14m kube-controller-manager 4.17.41 True False False 14m kube-scheduler 4.17.41 True False False 14m kube-storage-version-migrator 4.17.41 True False False 4m4s monitoring Unknown True Unknown 3m40s Rolling out the stack. network 4.17.41 True False False 14m node-tuning 4.17.41 True False False 4m42s openshift-apiserver 4.17.41 True False False 14m openshift-controller-manager 4.17.41 True False False 14m openshift-samples 4.17.41 True False False 3m23s operator-lifecycle-manager 4.17.41 True False False 14m operator-lifecycle-manager-catalog 4.17.41 True False False 14m operator-lifecycle-manager-packageserver 4.17.41 True False False 14m service-ca 4.17.41 True False False 4m7s storage 4.17.41 True False False 4m39s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 3m58s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 15m dns 4.17.41 True False False 4m35s image-registry True True True 4m29s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 4m11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 5m9s kube-apiserver 4.17.41 True False False 15m kube-controller-manager 4.17.41 True False False 15m kube-scheduler 4.17.41 True False False 15m kube-storage-version-migrator 4.17.41 True False False 5m4s monitoring Unknown True Unknown 4m40s Rolling out the stack. network 4.17.41 True False False 15m node-tuning 4.17.41 True False False 5m42s openshift-apiserver 4.17.41 True False False 15m openshift-controller-manager 4.17.41 True False False 15m openshift-samples 4.17.41 True False False 4m23s operator-lifecycle-manager 4.17.41 True False False 15m operator-lifecycle-manager-catalog 4.17.41 True False False 15m operator-lifecycle-manager-packageserver 4.17.41 True False False 15m service-ca 4.17.41 True False False 5m7s storage 4.17.41 True False False 5m39s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 4m58s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 16m dns 4.17.41 True False False 5m35s image-registry True True True 5m29s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 5m11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 6m9s kube-apiserver 4.17.41 True False False 16m kube-controller-manager 4.17.41 True False False 16m kube-scheduler 4.17.41 True False False 16m kube-storage-version-migrator 4.17.41 True False False 6m4s monitoring Unknown True Unknown 5m40s Rolling out the stack. network 4.17.41 True False False 16m node-tuning 4.17.41 True False False 6m42s openshift-apiserver 4.17.41 True False False 16m openshift-controller-manager 4.17.41 True False False 16m openshift-samples 4.17.41 True False False 5m23s operator-lifecycle-manager 4.17.41 True False False 16m operator-lifecycle-manager-catalog 4.17.41 True False False 16m operator-lifecycle-manager-packageserver 4.17.41 True False False 16m service-ca 4.17.41 True False False 6m7s storage 4.17.41 True False False 6m39s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 5m59s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 17m dns 4.17.41 True False False 6m36s image-registry True True True 6m30s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 6m12s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 7m10s kube-apiserver 4.17.41 True False False 17m kube-controller-manager 4.17.41 True False False 17m kube-scheduler 4.17.41 True False False 17m kube-storage-version-migrator 4.17.41 True False False 7m5s monitoring Unknown True Unknown 6m41s Rolling out the stack. network 4.17.41 True False False 17m node-tuning 4.17.41 True False False 7m43s openshift-apiserver 4.17.41 True False False 17m openshift-controller-manager 4.17.41 True False False 17m openshift-samples 4.17.41 True False False 6m24s operator-lifecycle-manager 4.17.41 True False False 17m operator-lifecycle-manager-catalog 4.17.41 True False False 17m operator-lifecycle-manager-packageserver 4.17.41 True False False 17m service-ca 4.17.41 True False False 7m8s storage 4.17.41 True False False 7m40s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 6m59s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 18m dns 4.17.41 True True False 7m36s DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2." image-registry True True True 7m30s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 7m12s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 8m10s kube-apiserver 4.17.41 True False False 18m kube-controller-manager 4.17.41 True False False 18m kube-scheduler 4.17.41 True False False 18m kube-storage-version-migrator 4.17.41 True False False 8m5s monitoring Unknown True Unknown 7m41s Rolling out the stack. network 4.17.41 True True False 18m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.17.41 True True False 19s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.41 True False False 18m openshift-controller-manager 4.17.41 True False False 18m openshift-samples 4.17.41 True False False 7m24s operator-lifecycle-manager 4.17.41 True False False 18m operator-lifecycle-manager-catalog 4.17.41 True False False 18m operator-lifecycle-manager-packageserver 4.17.41 True False False 18m service-ca 4.17.41 True False False 8m8s storage 4.17.41 True True False 8m40s AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True True False 7m59s SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 19m dns 4.17.41 True False False 8m36s image-registry True True True 8m30s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-54857874dd" has timed out progressing. ingress 4.17.41 True True False 8m12s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.41 True False False 9m10s kube-apiserver 4.17.41 True False False 19m kube-controller-manager 4.17.41 True False False 19m kube-scheduler 4.17.41 True False False 19m kube-storage-version-migrator 4.17.41 True False False 9m5s monitoring Unknown True Unknown 8m41s Rolling out the stack. network 4.17.41 True True False 19m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.17.41 True False False 79s openshift-apiserver 4.17.41 True False False 19m openshift-controller-manager 4.17.41 True False False 19m openshift-samples 4.17.41 True False False 8m24s operator-lifecycle-manager 4.17.41 True False False 19m operator-lifecycle-manager-catalog 4.17.41 True False False 19m operator-lifecycle-manager-packageserver 4.17.41 True False False 19m service-ca 4.17.41 True False False 9m8s storage 4.17.41 True False False 9m40s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.41 True False False 8m59s csi-snapshot-controller 4.17.41 True False False 20m dns 4.17.41 True False False 9m36s image-registry 4.17.41 True False False 9m30s ingress 4.17.41 True False False 9m12s insights 4.17.41 True False False 10m kube-apiserver 4.17.41 True False False 20m kube-controller-manager 4.17.41 True False False 20m kube-scheduler 4.17.41 True False False 20m kube-storage-version-migrator 4.17.41 True False False 10m monitoring Unknown True Unknown 9m41s Rolling out the stack. network 4.17.41 True False False 20m node-tuning 4.17.41 True False False 2m19s openshift-apiserver 4.17.41 True False False 20m openshift-controller-manager 4.17.41 True False False 20m openshift-samples 4.17.41 True False False 9m24s operator-lifecycle-manager 4.17.41 True False False 20m operator-lifecycle-manager-catalog 4.17.41 True False False 20m operator-lifecycle-manager-packageserver 4.17.41 True False False 20m service-ca 4.17.41 True False False 10m storage 4.17.41 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.17.41 True True False 10m SyncLoopRefreshProgressing: working toward version 4.17.41, 1 replicas available csi-snapshot-controller 4.17.41 True False False 21m dns 4.17.41 True False False 10m image-registry 4.17.41 True False False 10m ingress 4.17.41 True False False 10m insights 4.17.41 True False False 11m kube-apiserver 4.17.41 True False False 21m kube-controller-manager 4.17.41 True False False 21m kube-scheduler 4.17.41 True False False 21m kube-storage-version-migrator 4.17.41 True False False 11m monitoring 4.17.41 True False False 2s network 4.17.41 True True False 21m DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.17.41 True False False 35s openshift-apiserver 4.17.41 True False False 21m openshift-controller-manager 4.17.41 True False False 21m openshift-samples 4.17.41 True False False 10m operator-lifecycle-manager 4.17.41 True False False 21m operator-lifecycle-manager-catalog 4.17.41 True False False 21m operator-lifecycle-manager-packageserver 4.17.41 True False False 21m service-ca 4.17.41 True False False 11m storage 4.17.41 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.17.41 True False False 11m csi-snapshot-controller 4.17.41 True False False 22m dns 4.17.41 True False False 11m image-registry 4.17.41 True False False 11m ingress 4.17.41 True False False 11m insights 4.17.41 True False False 12m kube-apiserver 4.17.41 True False False 22m kube-controller-manager 4.17.41 True False False 22m kube-scheduler 4.17.41 True False False 22m kube-storage-version-migrator 4.17.41 True False False 12m monitoring 4.17.41 True False False 62s network 4.17.41 True False False 22m node-tuning 4.17.41 True False False 95s openshift-apiserver 4.17.41 True False False 22m openshift-controller-manager 4.17.41 True False False 22m openshift-samples 4.17.41 True False False 11m operator-lifecycle-manager 4.17.41 True False False 22m operator-lifecycle-manager-catalog 4.17.41 True False False 22m operator-lifecycle-manager-packageserver 4.17.41 True False False 22m service-ca 4.17.41 True False False 12m storage 4.17.41 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.17.41 True False False 12m csi-snapshot-controller 4.17.41 True False False 23m dns 4.17.41 True False False 12m image-registry 4.17.41 True False False 12m ingress 4.17.41 True False False 12m insights 4.17.41 True False False 13m kube-apiserver 4.17.41 True False False 23m kube-controller-manager 4.17.41 True False False 23m kube-scheduler 4.17.41 True False False 23m kube-storage-version-migrator 4.17.41 True False False 13m monitoring 4.17.41 True False False 2m2s network 4.17.41 True False False 23m node-tuning 4.17.41 True False False 2m35s openshift-apiserver 4.17.41 True False False 23m openshift-controller-manager 4.17.41 True False False 23m openshift-samples 4.17.41 True False False 12m operator-lifecycle-manager 4.17.41 True False False 23m operator-lifecycle-manager-catalog 4.17.41 True False False 23m operator-lifecycle-manager-packageserver 4.17.41 True False False 23m service-ca 4.17.41 True False False 13m storage 4.17.41 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.17.41 True False False 13m csi-snapshot-controller 4.17.41 True False False 24m dns 4.17.41 True False False 13m image-registry 4.17.41 True False False 13m ingress 4.17.41 True False False 13m insights 4.17.41 True False False 14m kube-apiserver 4.17.41 True False False 24m kube-controller-manager 4.17.41 True False False 24m kube-scheduler 4.17.41 True False False 24m kube-storage-version-migrator 4.17.41 True False False 14m monitoring 4.17.41 True False False 3m2s network 4.17.41 True False False 24m node-tuning 4.17.41 True False False 3m35s openshift-apiserver 4.17.41 True False False 24m openshift-controller-manager 4.17.41 True False False 24m openshift-samples 4.17.41 True False False 13m operator-lifecycle-manager 4.17.41 True False False 24m operator-lifecycle-manager-catalog 4.17.41 True False False 24m operator-lifecycle-manager-packageserver 4.17.41 True False False 24m service-ca 4.17.41 True False False 14m storage 4.17.41 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.17.41 True False False 14m csi-snapshot-controller 4.17.41 True False False 25m dns 4.17.41 True False False 14m image-registry 4.17.41 True False False 14m ingress 4.17.41 True False False 14m insights 4.17.41 True False False 15m kube-apiserver 4.17.41 True False False 25m kube-controller-manager 4.17.41 True False False 25m kube-scheduler 4.17.41 True False False 25m kube-storage-version-migrator 4.17.41 True False False 15m monitoring 4.17.41 True False False 4m3s network 4.17.41 True False False 25m node-tuning 4.17.41 True False False 4m36s openshift-apiserver 4.17.41 True False False 25m openshift-controller-manager 4.17.41 True False False 25m openshift-samples 4.17.41 True False False 14m operator-lifecycle-manager 4.17.41 True False False 25m operator-lifecycle-manager-catalog 4.17.41 True False False 25m operator-lifecycle-manager-packageserver 4.17.41 True False False 25m service-ca 4.17.41 True False False 15m storage 4.17.41 True False False 15m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!