INFO: Log in to your Red Hat account... INFO: Configure AWS Credentials... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Logged in as 'rhtap-shared' on 'https://api.openshift.com' INFO: Create ROSA with HCP cluster... WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-d255bcc8f9' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-d255bcc8f9' 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-d255bcc8f9 Domain Prefix: kx-d255bcc8f9 Display Name: kx-d255bcc8f9 ID: 2md4jv66qioj64bk4cga98jlvrnkkd34 External ID: 258e9111-00f0-485c-97ea-eab4a92be82a Control Plane: ROSA Service Hosted OpenShift Version: 4.17.42 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-kube-system-kube-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-capa-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-control-plane-operator - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kms-provider - arn:aws:iam::381492310364:role/rhads-hcp-openshift-image-registry-installer-cloud-credentials - 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 Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Nov 6 2025 12:43:43 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/356aYcMb1IBgeLJCVxWRLX668kn OIDC Endpoint URL: https://oidc.op1.openshiftapps.com/2jtsga3i2etnl697l7bk5i1kmbm4a95j (Managed) Etcd Encryption: Disabled Audit Log Forwarding: Disabled External Authentication: Disabled Zero Egress: Disabled INFO: Preparing to create operator roles. INFO: Operator Roles already exists INFO: Preparing to create OIDC Provider. INFO: OIDC provider already exists INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-d255bcc8f9'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-d255bcc8f9 --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-d255bcc8f9' 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-d255bcc8f9 Version 2025-11-06 12:49:52 +0000 UTC hostedclusters kx-d255bcc8f9 ValidAWSIdentityProvider StatusUnknown 2025-11-06 12:49:53 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-11-06 12:49:53 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Ignition server deployment not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is supported by operator configuration 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Release image is valid 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation active on resource 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is not found 2025-11-06 12:49:55 +0000 UTC hostedclusters kx-d255bcc8f9 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-11-06 12:49:55 +0000 UTC hostedclusters kx-d255bcc8f9 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-d255bcc8f9 Version 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Release image is valid 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Waiting for hosted control plane kubeconfig to be created 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation active on resource 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is supported by operator configuration 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Ignition server deployment not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:55 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is at expected version 2025-11-06 12:51:22 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-11-06 12:51:31 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:32 +0000 UTC hostedclusters kx-d255bcc8f9 Required platform credentials are found 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 AWS KMS is not configured 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 lookup api.kx-d255bcc8f9.2hzl.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 Waiting for etcd to reach quorum 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 Kube APIServer deployment not found 2025-11-06 12:51:35 +0000 UTC hostedclusters kx-d255bcc8f9 capi-provider deployment has 1 unavailable replicas 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 OIDC configuration is valid 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation completed successfully 2025-11-06 12:51:43 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:51:56 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:52:03 +0000 UTC hostedclusters kx-d255bcc8f9 WebIdentityErr 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-d255bcc8f9 Version 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Release image is valid 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 APIServer external route not admitted 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation active on resource 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is supported by operator configuration 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Ignition server deployment not found 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:49:55 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is at expected version 2025-11-06 12:51:22 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-11-06 12:51:31 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:32 +0000 UTC hostedclusters kx-d255bcc8f9 Required platform credentials are found 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 AWS KMS is not configured 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 lookup api.kx-d255bcc8f9.2hzl.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:35 +0000 UTC hostedclusters kx-d255bcc8f9 [capi-provider deployment has 2 unavailable replicas, openshift-apiserver deployment has 3 unavailable replicas] 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 OIDC configuration is valid 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation completed successfully 2025-11-06 12:51:43 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:51:56 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:52:24 +0000 UTC hostedclusters kx-d255bcc8f9 EtcdAvailable QuorumAvailable 2025-11-06 12:52:48 +0000 UTC hostedclusters kx-d255bcc8f9 Kube APIServer deployment is available 2025-11-06 12:53:04 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:53:10 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:53:11 +0000 UTC hostedclusters kx-d255bcc8f9 Ignition server deployment is available 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 ClusterVersionSucceeding FromClusterVersion 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Payload loaded version="4.17.42" image="quay.io/openshift-release-dev/ocp-release@sha256:9b7b9909a1f064d5238f35f6e5fc9ac275a0d463a74e8c545544755d953a46d9" architecture="Multi" 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 ClusterVersionAvailable FromClusterVersion 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Working towards 4.17.42: 526 of 621 done (84% complete) 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-d255bcc8f9 Version 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation active on resource 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Get "https://a5fd55006df734db199518ea0ba153b8-038ea479c3b33647.elb.us-east-1.amazonaws.com:443/healthz": dial tcp: lookup a5fd55006df734db199518ea0ba153b8-038ea479c3b33647.elb.us-east-1.amazonaws.com on 172.30.0.10:53: no such host 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Release image is valid 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is supported by operator configuration 2025-11-06 12:49:55 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is at expected version 2025-11-06 12:51:22 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-11-06 12:51:31 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:32 +0000 UTC hostedclusters kx-d255bcc8f9 Required platform credentials are found 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 AWS KMS is not configured 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 lookup api.kx-d255bcc8f9.2hzl.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation completed successfully 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 OIDC configuration is valid 2025-11-06 12:51:43 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:51:56 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:52:24 +0000 UTC hostedclusters kx-d255bcc8f9 EtcdAvailable QuorumAvailable 2025-11-06 12:52:48 +0000 UTC hostedclusters kx-d255bcc8f9 Kube APIServer deployment is available 2025-11-06 12:53:04 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:53:10 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:53:11 +0000 UTC hostedclusters kx-d255bcc8f9 Ignition server deployment is available 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Payload loaded version="4.17.42" image="quay.io/openshift-release-dev/ocp-release@sha256:9b7b9909a1f064d5238f35f6e5fc9ac275a0d463a74e8c545544755d953a46d9" architecture="Multi" 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 ClusterVersionAvailable FromClusterVersion 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Unable to apply 4.17.42: some cluster operators are not available 2025-11-06 12:53:57 +0000 UTC hostedclusters kx-d255bcc8f9 Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-11-06 12:54:23 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted cluster is not degraded 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-d255bcc8f9 Version 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation active on resource 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 Release image is valid 2025-11-06 12:49:54 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is supported by operator configuration 2025-11-06 12:49:55 +0000 UTC hostedclusters kx-d255bcc8f9 HostedCluster is at expected version 2025-11-06 12:51:22 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-11-06 12:51:31 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:32 +0000 UTC hostedclusters kx-d255bcc8f9 Required platform credentials are found 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 Configuration passes validation 2025-11-06 12:51:34 +0000 UTC hostedclusters kx-d255bcc8f9 AWS KMS is not configured 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 OIDC configuration is valid 2025-11-06 12:51:37 +0000 UTC hostedclusters kx-d255bcc8f9 Reconciliation completed successfully 2025-11-06 12:51:43 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:51:56 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:52:24 +0000 UTC hostedclusters kx-d255bcc8f9 EtcdAvailable QuorumAvailable 2025-11-06 12:52:48 +0000 UTC hostedclusters kx-d255bcc8f9 Kube APIServer deployment is available 2025-11-06 12:53:04 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:53:10 +0000 UTC hostedclusters kx-d255bcc8f9 All is well 2025-11-06 12:53:11 +0000 UTC hostedclusters kx-d255bcc8f9 Ignition server deployment is available 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Payload loaded version="4.17.42" image="quay.io/openshift-release-dev/ocp-release@sha256:9b7b9909a1f064d5238f35f6e5fc9ac275a0d463a74e8c545544755d953a46d9" architecture="Multi" 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 ClusterVersionAvailable FromClusterVersion 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Unable to apply 4.17.42: some cluster operators are not available 2025-11-06 12:53:21 +0000 UTC hostedclusters kx-d255bcc8f9 Condition not found in the CVO. 2025-11-06 12:53:57 +0000 UTC hostedclusters kx-d255bcc8f9 Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-11-06 12:54:42 +0000 UTC hostedclusters kx-d255bcc8f9 The hosted control plane is available INFO: Cluster 'kx-d255bcc8f9' 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... Unable to connect to the server: dial tcp: lookup api.kx-d255bcc8f9.2hzl.p3.openshiftapps.com on 172.30.0.10:53: no such host Waiting for cluster operators to be accessible... Trying again in 10s Unable to connect to the server: dial tcp: lookup api.kx-d255bcc8f9.2hzl.p3.openshiftapps.com on 172.30.0.10:53: no such host Waiting for cluster operators to be accessible... Trying again in 10s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 4m38s dns 4.17.42 False False True 4m39s DNS "default" is unavailable. image-registry False True True 4m25s Available: The deployment does not have available replicas... ingress False True True 4m23s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 4m29s kube-controller-manager 4.17.42 True False False 4m29s kube-scheduler 4.17.42 True False False 4m29s kube-storage-version-migrator monitoring network 4.17.42 True True False 4m15s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m24s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 4m29s openshift-controller-manager 4.17.42 True False False 4m29s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m31s operator-lifecycle-manager-catalog 4.17.42 True False False 4m22s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m29s service-ca storage 4.17.42 False False False 4m29s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service cluster operators to be accessible finished! [INFO] Cluster operators are accessible. Waiting for cluster to be reported as healthy for 60m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 4m38s dns 4.17.42 False False True 4m39s DNS "default" is unavailable. image-registry False True True 4m25s Available: The deployment does not have available replicas... ingress False True True 4m23s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 4m29s kube-controller-manager 4.17.42 True False False 4m29s kube-scheduler 4.17.42 True False False 4m29s kube-storage-version-migrator monitoring network 4.17.42 True True False 4m15s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m24s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 4m29s openshift-controller-manager 4.17.42 True False False 4m29s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m31s operator-lifecycle-manager-catalog 4.17.42 True False False 4m22s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m29s service-ca storage 4.17.42 False False False 4m29s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 5m38s dns 4.17.42 False False True 5m39s DNS "default" is unavailable. image-registry False True True 5m25s Available: The deployment does not have available replicas... ingress False True True 5m23s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 5m29s kube-controller-manager 4.17.42 True False False 5m29s kube-scheduler 4.17.42 True False False 5m29s kube-storage-version-migrator monitoring network 4.17.42 True True False 5m15s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 5m24s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 5m29s openshift-controller-manager 4.17.42 True False False 5m29s openshift-samples operator-lifecycle-manager 4.17.42 True False False 5m31s operator-lifecycle-manager-catalog 4.17.42 True False False 5m22s operator-lifecycle-manager-packageserver 4.17.42 True False False 5m29s service-ca storage 4.17.42 False False False 5m29s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 6m39s dns 4.17.42 False False True 6m40s DNS "default" is unavailable. image-registry False True True 6m26s Available: The deployment does not have available replicas... ingress False True True 6m24s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 6m30s kube-controller-manager 4.17.42 True False False 6m30s kube-scheduler 4.17.42 True False False 6m30s kube-storage-version-migrator monitoring network 4.17.42 True True False 6m16s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.17.42 True True False 3s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.17.42 True False False 6m30s openshift-controller-manager 4.17.42 True False False 6m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 6m32s operator-lifecycle-manager-catalog 4.17.42 True False False 6m23s operator-lifecycle-manager-packageserver 4.17.42 True False False 6m30s service-ca storage 4.17.42 False True False 6m30s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 Unknown False False 5s csi-snapshot-controller 4.17.42 True False False 7m39s dns 4.17.42 False True True 7m40s DNS "default" is unavailable. image-registry False True True 7m26s Available: The deployment does not have available replicas... ingress False True True 7m24s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.17.42 True False False 24s kube-apiserver 4.17.42 True False False 7m30s kube-controller-manager 4.17.42 True False False 7m30s kube-scheduler 4.17.42 True False False 7m30s kube-storage-version-migrator 4.17.42 True False False 20s monitoring network 4.17.42 True True False 7m16s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True False False 63s openshift-apiserver 4.17.42 True False False 7m30s openshift-controller-manager 4.17.42 True False False 7m30s openshift-samples operator-lifecycle-manager 4.17.42 True False False 7m32s operator-lifecycle-manager-catalog 4.17.42 True False False 7m23s operator-lifecycle-manager-packageserver 4.17.42 True False False 7m30s service-ca 4.17.42 True False False 21s storage 4.17.42 True False False 60s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 24s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 8m39s dns 4.17.42 True False False 24s image-registry True True False 18s Progressing: The deployment has not completed... ingress 4.17.42 False True False 26s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.17.42 True False False 84s kube-apiserver 4.17.42 True False False 8m30s kube-controller-manager 4.17.42 True False False 8m30s kube-scheduler 4.17.42 True False False 8m30s kube-storage-version-migrator 4.17.42 True False False 80s monitoring Unknown True Unknown 56s Rolling out the stack. network 4.17.42 True True False 8m16s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 10s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 8m30s openshift-controller-manager 4.17.42 True False False 8m30s openshift-samples 4.17.42 True False False 20s operator-lifecycle-manager 4.17.42 True False False 8m32s operator-lifecycle-manager-catalog 4.17.42 True False False 8m23s operator-lifecycle-manager-packageserver 4.17.42 True False False 8m30s service-ca 4.17.42 True False False 81s storage 4.17.42 True True False 2m AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 84s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 9m39s dns 4.17.42 True False False 84s image-registry True True True 78s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 6s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 2m24s kube-apiserver 4.17.42 True False False 9m30s kube-controller-manager 4.17.42 True False False 9m30s kube-scheduler 4.17.42 True False False 9m30s kube-storage-version-migrator 4.17.42 True False False 2m20s monitoring Unknown True Unknown 116s Rolling out the stack. network 4.17.42 True True False 9m16s DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 70s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 9m30s openshift-controller-manager 4.17.42 True False False 9m30s openshift-samples 4.17.42 True False False 80s operator-lifecycle-manager 4.17.42 True False False 9m32s operator-lifecycle-manager-catalog 4.17.42 True False False 9m23s operator-lifecycle-manager-packageserver 4.17.42 True False False 9m30s service-ca 4.17.42 True False False 2m21s storage 4.17.42 True False False 3m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 2m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 10m dns 4.17.42 True False False 2m25s image-registry True True True 2m19s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 67s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 3m25s kube-apiserver 4.17.42 True False False 10m kube-controller-manager 4.17.42 True False False 10m kube-scheduler 4.17.42 True False False 10m kube-storage-version-migrator 4.17.42 True False False 3m21s monitoring Unknown True Unknown 2m57s Rolling out the stack. network 4.17.42 True True False 10m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 2m11s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 10m openshift-controller-manager 4.17.42 True False False 10m openshift-samples 4.17.42 True False False 2m21s operator-lifecycle-manager 4.17.42 True False False 10m operator-lifecycle-manager-catalog 4.17.42 True False False 10m operator-lifecycle-manager-packageserver 4.17.42 True False False 10m service-ca 4.17.42 True False False 3m22s storage 4.17.42 True False False 4m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 3m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 11m dns 4.17.42 True False False 3m25s image-registry True True True 3m19s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 2m7s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 4m25s kube-apiserver 4.17.42 True False False 11m kube-controller-manager 4.17.42 True False False 11m kube-scheduler 4.17.42 True False False 11m kube-storage-version-migrator 4.17.42 True False False 4m21s monitoring Unknown True Unknown 3m57s Rolling out the stack. network 4.17.42 True True False 11m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 3m11s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 11m openshift-controller-manager 4.17.42 True False False 11m openshift-samples 4.17.42 True False False 3m21s operator-lifecycle-manager 4.17.42 True False False 11m operator-lifecycle-manager-catalog 4.17.42 True False False 11m operator-lifecycle-manager-packageserver 4.17.42 True False False 11m service-ca 4.17.42 True False False 4m22s storage 4.17.42 True False False 5m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 4m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 12m dns 4.17.42 True False False 4m25s image-registry True True True 4m19s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 3m7s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 5m25s kube-apiserver 4.17.42 True False False 12m kube-controller-manager 4.17.42 True False False 12m kube-scheduler 4.17.42 True False False 12m kube-storage-version-migrator 4.17.42 True False False 5m21s monitoring Unknown True Unknown 4m57s Rolling out the stack. network 4.17.42 True True False 12m DaemonSet "/openshift-multus/multus" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 4m11s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 12m openshift-controller-manager 4.17.42 True False False 12m openshift-samples 4.17.42 True False False 4m21s operator-lifecycle-manager 4.17.42 True False False 12m operator-lifecycle-manager-catalog 4.17.42 True False False 12m operator-lifecycle-manager-packageserver 4.17.42 True False False 12m service-ca 4.17.42 True False False 5m22s storage 4.17.42 True False False 6m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 5m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 13m dns 4.17.42 True False False 5m25s image-registry True True True 5m19s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 4m7s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 6m25s kube-apiserver 4.17.42 True False False 13m kube-controller-manager 4.17.42 True False False 13m kube-scheduler 4.17.42 True False False 13m kube-storage-version-migrator 4.17.42 True False False 6m21s monitoring Unknown True Unknown 5m57s Rolling out the stack. network 4.17.42 True True False 13m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 5m11s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 13m openshift-controller-manager 4.17.42 True False False 13m openshift-samples 4.17.42 True False False 5m21s operator-lifecycle-manager 4.17.42 True False False 13m operator-lifecycle-manager-catalog 4.17.42 True False False 13m operator-lifecycle-manager-packageserver 4.17.42 True False False 13m service-ca 4.17.42 True False False 6m22s storage 4.17.42 True False False 7m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 6m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 14m dns 4.17.42 True False False 6m26s image-registry True True True 6m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 5m8s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 7m26s kube-apiserver 4.17.42 True False False 14m kube-controller-manager 4.17.42 True False False 14m kube-scheduler 4.17.42 True False False 14m kube-storage-version-migrator 4.17.42 True False False 7m22s monitoring Unknown True Unknown 6m58s Rolling out the stack. network 4.17.42 True True False 14m DaemonSet "/openshift-multus/multus" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 6m12s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 14m openshift-controller-manager 4.17.42 True False False 14m openshift-samples 4.17.42 True False False 6m22s operator-lifecycle-manager 4.17.42 True False False 14m operator-lifecycle-manager-catalog 4.17.42 True False False 14m operator-lifecycle-manager-packageserver 4.17.42 True False False 14m service-ca 4.17.42 True False False 7m23s storage 4.17.42 True False False 8m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 7m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 15m dns 4.17.42 True False False 7m26s image-registry True True True 7m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 6m8s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 8m26s kube-apiserver 4.17.42 True False False 15m kube-controller-manager 4.17.42 True False False 15m kube-scheduler 4.17.42 True False False 15m kube-storage-version-migrator 4.17.42 True False False 8m22s monitoring Unknown True Unknown 7m58s Rolling out the stack. network 4.17.42 True True True 15m DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress - pod ovnkube-node-lfnvh is in CrashLoopBackOff State node-tuning 4.17.42 True True False 7m12s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 15m openshift-controller-manager 4.17.42 True False False 15m openshift-samples 4.17.42 True False False 7m22s operator-lifecycle-manager 4.17.42 True False False 15m operator-lifecycle-manager-catalog 4.17.42 True False False 15m operator-lifecycle-manager-packageserver 4.17.42 True False False 15m service-ca 4.17.42 True False False 8m23s storage 4.17.42 True False False 9m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 8m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 16m dns 4.17.42 True False False 8m26s image-registry True True True 8m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 7m8s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 9m26s kube-apiserver 4.17.42 True False False 16m kube-controller-manager 4.17.42 True False False 16m kube-scheduler 4.17.42 True False False 16m kube-storage-version-migrator 4.17.42 True False False 9m22s monitoring Unknown True Unknown 8m58s Rolling out the stack. network 4.17.42 True True True 16m DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress - pod ovnkube-node-l92vd is in CrashLoopBackOff State node-tuning 4.17.42 True True False 8m12s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 16m openshift-controller-manager 4.17.42 True False False 16m openshift-samples 4.17.42 True False False 8m22s operator-lifecycle-manager 4.17.42 True False False 16m operator-lifecycle-manager-catalog 4.17.42 True False False 16m operator-lifecycle-manager-packageserver 4.17.42 True False False 16m service-ca 4.17.42 True False False 9m23s storage 4.17.42 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.42 True True False 9m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 17m dns 4.17.42 True False False 9m26s image-registry True True True 9m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 8m8s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 10m kube-apiserver 4.17.42 True False False 17m kube-controller-manager 4.17.42 True False False 17m kube-scheduler 4.17.42 True False False 17m kube-storage-version-migrator 4.17.42 True False False 10m monitoring Unknown True Unknown 9m58s Rolling out the stack. network 4.17.42 True True True 17m DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress - pod ovnkube-node-l92vd is in CrashLoopBackOff State node-tuning 4.17.42 True True False 9m12s Waiting for 2/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 17m openshift-controller-manager 4.17.42 True False False 17m openshift-samples 4.17.42 True False False 9m22s operator-lifecycle-manager 4.17.42 True False False 17m operator-lifecycle-manager-catalog 4.17.42 True False False 17m operator-lifecycle-manager-packageserver 4.17.42 True False False 17m service-ca 4.17.42 True False False 10m storage 4.17.42 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.42 True True False 10m SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 18m dns 4.17.42 True False False 10m image-registry True True True 10m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 9m9s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 11m kube-apiserver 4.17.42 True False False 18m kube-controller-manager 4.17.42 True False False 18m kube-scheduler 4.17.42 True False False 18m kube-storage-version-migrator 4.17.42 True False False 11m monitoring Unknown True Unknown 10m Rolling out the stack. network 4.17.42 True False False 18m node-tuning 4.17.42 True False False 4s openshift-apiserver 4.17.42 True False False 18m openshift-controller-manager 4.17.42 True False False 18m openshift-samples 4.17.42 True False False 10m operator-lifecycle-manager 4.17.42 True False False 18m operator-lifecycle-manager-catalog 4.17.42 True False False 18m operator-lifecycle-manager-packageserver 4.17.42 True False False 18m service-ca 4.17.42 True False False 11m storage 4.17.42 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.42 True True False 11m SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 19m dns 4.17.42 True False False 11m image-registry True True True 11m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 10m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 12m kube-apiserver 4.17.42 True False False 19m kube-controller-manager 4.17.42 True False False 19m kube-scheduler 4.17.42 True False False 19m kube-storage-version-migrator 4.17.42 True False False 12m monitoring Unknown True Unknown 11m Rolling out the stack. network 4.17.42 True False False 19m node-tuning 4.17.42 True False False 64s openshift-apiserver 4.17.42 True False False 19m openshift-controller-manager 4.17.42 True False False 19m openshift-samples 4.17.42 True False False 11m operator-lifecycle-manager 4.17.42 True False False 19m operator-lifecycle-manager-catalog 4.17.42 True False False 19m operator-lifecycle-manager-packageserver 4.17.42 True False False 19m service-ca 4.17.42 True False False 12m storage 4.17.42 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.42 True True False 12m SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 20m dns 4.17.42 True False False 12m image-registry True True True 12m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 True True False 11m ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 13m kube-apiserver 4.17.42 True False False 20m kube-controller-manager 4.17.42 True False False 20m kube-scheduler 4.17.42 True False False 20m kube-storage-version-migrator 4.17.42 True False False 13m monitoring Unknown True Unknown 13m Rolling out the stack. network 4.17.42 True False False 20m node-tuning 4.17.42 True False False 2m5s openshift-apiserver 4.17.42 True False False 20m openshift-controller-manager 4.17.42 True False False 20m openshift-samples 4.17.42 True False False 12m operator-lifecycle-manager 4.17.42 True False False 20m operator-lifecycle-manager-catalog 4.17.42 True False False 20m operator-lifecycle-manager-packageserver 4.17.42 True False False 20m service-ca 4.17.42 True False False 13m storage 4.17.42 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.42 True False False 13m csi-snapshot-controller 4.17.42 True False False 21m dns 4.17.42 True False True 13m DNS default is degraded image-registry True True True 13m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-65d7445548" has timed out progressing. ingress 4.17.42 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 of 2 updated replica(s) are available...... insights 4.17.42 True False False 14m kube-apiserver 4.17.42 True False False 21m kube-controller-manager 4.17.42 True False False 21m kube-scheduler 4.17.42 True False False 21m kube-storage-version-migrator 4.17.42 True False False 14m monitoring Unknown True Unknown 14m Rolling out the stack. network 4.17.42 True True False 21m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes) node-tuning 4.17.42 True False False 45s openshift-apiserver 4.17.42 True False False 21m openshift-controller-manager 4.17.42 True False False 21m openshift-samples 4.17.42 True False False 13m operator-lifecycle-manager 4.17.42 True False False 21m operator-lifecycle-manager-catalog 4.17.42 True False False 21m operator-lifecycle-manager-packageserver 4.17.42 True False False 21m service-ca 4.17.42 True False False 14m storage 4.17.42 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.17.42 True False False 14m csi-snapshot-controller 4.17.42 True False False 22m dns 4.17.42 True False False 14m image-registry 4.17.42 True False False 14m ingress 4.17.42 True False False 13m insights 4.17.42 True False False 15m kube-apiserver 4.17.42 True False False 22m kube-controller-manager 4.17.42 True False False 22m kube-scheduler 4.17.42 True False False 22m kube-storage-version-migrator 4.17.42 True False False 15m monitoring Unknown True Unknown 15m Rolling out the stack. network 4.17.42 True False False 22m node-tuning 4.17.42 True False False 105s openshift-apiserver 4.17.42 True False False 22m openshift-controller-manager 4.17.42 True False False 22m openshift-samples 4.17.42 True False False 14m operator-lifecycle-manager 4.17.42 True False False 22m operator-lifecycle-manager-catalog 4.17.42 True False False 22m operator-lifecycle-manager-packageserver 4.17.42 True False False 22m service-ca 4.17.42 True False False 15m storage 4.17.42 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.17.42 True False False 15m csi-snapshot-controller 4.17.42 True False False 23m dns 4.17.42 True False False 15m image-registry 4.17.42 True False False 15m ingress 4.17.42 True False False 14m insights 4.17.42 True False False 16m kube-apiserver 4.17.42 True False False 23m kube-controller-manager 4.17.42 True False False 23m kube-scheduler 4.17.42 True False False 23m kube-storage-version-migrator 4.17.42 True False False 16m monitoring 4.17.42 True False False 8s network 4.17.42 True False False 23m node-tuning 4.17.42 True False False 2m46s openshift-apiserver 4.17.42 True False False 23m openshift-controller-manager 4.17.42 True False False 23m openshift-samples 4.17.42 True False False 15m operator-lifecycle-manager 4.17.42 True False False 23m operator-lifecycle-manager-catalog 4.17.42 True False False 23m operator-lifecycle-manager-packageserver 4.17.42 True False False 23m service-ca 4.17.42 True False False 16m storage 4.17.42 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.17.42 True True False 16m SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 24m dns 4.17.42 True False False 16m image-registry 4.17.42 True False False 16m ingress 4.17.42 True False False 15m insights 4.17.42 True False False 17m kube-apiserver 4.17.42 True False False 24m kube-controller-manager 4.17.42 True False False 24m kube-scheduler 4.17.42 True False False 24m kube-storage-version-migrator 4.17.42 True False False 17m monitoring 4.17.42 True False False 68s network 4.17.42 True False False 24m node-tuning 4.17.42 True False False 3m46s openshift-apiserver 4.17.42 True False False 24m openshift-controller-manager 4.17.42 True False False 24m openshift-samples 4.17.42 True False False 16m operator-lifecycle-manager 4.17.42 True False False 24m operator-lifecycle-manager-catalog 4.17.42 True False False 24m operator-lifecycle-manager-packageserver 4.17.42 True False False 24m service-ca 4.17.42 True False False 17m storage 4.17.42 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.17.42 True False False 17m csi-snapshot-controller 4.17.42 True False False 25m dns 4.17.42 True False False 17m image-registry 4.17.42 True False False 17m ingress 4.17.42 True False False 16m insights 4.17.42 True False False 18m kube-apiserver 4.17.42 True False False 25m kube-controller-manager 4.17.42 True False False 25m kube-scheduler 4.17.42 True False False 25m kube-storage-version-migrator 4.17.42 True False False 18m monitoring 4.17.42 True False False 2m8s network 4.17.42 True False False 25m node-tuning 4.17.42 True False False 4m46s openshift-apiserver 4.17.42 True False False 25m openshift-controller-manager 4.17.42 True False False 25m openshift-samples 4.17.42 True False False 17m operator-lifecycle-manager 4.17.42 True False False 25m operator-lifecycle-manager-catalog 4.17.42 True False False 25m operator-lifecycle-manager-packageserver 4.17.42 True False False 25m service-ca 4.17.42 True False False 18m storage 4.17.42 True False False 19m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 18m csi-snapshot-controller 4.17.42 True False False 26m dns 4.17.42 True False False 18m image-registry 4.17.42 True False False 18m ingress 4.17.42 True False False 17m insights 4.17.42 True False False 19m kube-apiserver 4.17.42 True False False 26m kube-controller-manager 4.17.42 True False False 26m kube-scheduler 4.17.42 True False False 26m kube-storage-version-migrator 4.17.42 True False False 19m monitoring 4.17.42 True False False 3m9s network 4.17.42 True False False 26m node-tuning 4.17.42 True False False 5m47s openshift-apiserver 4.17.42 True False False 26m openshift-controller-manager 4.17.42 True False False 26m openshift-samples 4.17.42 True False False 18m operator-lifecycle-manager 4.17.42 True False False 26m operator-lifecycle-manager-catalog 4.17.42 True False False 26m operator-lifecycle-manager-packageserver 4.17.42 True False False 26m service-ca 4.17.42 True False False 19m storage 4.17.42 True False False 20m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!