INFO: Log in to your Red Hat account... INFO: Configure AWS Credentials... INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com' INFO: Create ROSA with HCP cluster... WARN: The version of Red Hat OpenShift Service on AWS that you are installing will no longer be supported after '2025-11-02'. Red Hat recommends selecting a newer version. For more information, see https://docs.openshift.com/rosa/rosa_policy/rosa-life-cycle.html time=2025-09-14T08:41:25Z level=info msg=Ignored check for policy key 'sts_hcp_ec2_registry_permission_policy' (zero egress feature toggle is not enabled) INFO: Creating cluster 'kx-f54a93bc83' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-f54a93bc83' 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-f54a93bc83 Domain Prefix: kx-f54a93bc83 Display Name: kx-f54a93bc83 ID: 2la33eluul7cmdad493f1bl8ft9qco98 External ID: 3fc0a630-da5d-4336-ba4b-7d1d7ba58b55 Control Plane: ROSA Service Hosted OpenShift Version: 4.16.47 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-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 - 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-kms-provider Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Sep 14 2025 08:41:34 UTC User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/32gPZ1rVGWp730V8e995RiGr9sj 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-f54a93bc83'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-f54a93bc83 --watch'. INFO: Track the progress of the cluster creation... W: Region flag will be removed from this command in future versions INFO: Cluster 'kx-f54a93bc83' 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-f54a93bc83 Version 2025-09-14 08:45:10 +0000 UTC hostedclusters kx-f54a93bc83 ValidAWSIdentityProvider StatusUnknown 2025-09-14 08:45:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-09-14 08:45:11 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Ignition server deployment not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is supported by operator configuration 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Release image is valid 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation active on resource 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is not found 2025-09-14 08:45:16 +0000 UTC hostedclusters kx-f54a93bc83 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-14 08:45:17 +0000 UTC hostedclusters kx-f54a93bc83 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f54a93bc83 Version 2025-09-14 08:45:10 +0000 UTC hostedclusters kx-f54a93bc83 ValidAWSIdentityProvider StatusUnknown 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Release image is valid 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the HCP 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation active on resource 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Ignition server deployment not found 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is supported by operator configuration 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 router load balancer is not provisioned; 1s since creation.; private-router load balancer is not provisioned; 1s since creation.; router load balancer is not provisioned; 1s since creation. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:45:16 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is at expected version 2025-09-14 08:46:38 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-09-14 08:46:43 +0000 UTC hostedclusters kx-f54a93bc83 Configuration passes validation 2025-09-14 08:46:45 +0000 UTC hostedclusters kx-f54a93bc83 Required platform credentials are found 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 Configuration passes validation 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 AWS KMS is not configured 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 router load balancer is not provisioned; 1s since creation.; private-router load balancer is not provisioned; 1s since creation.; router load balancer is not provisioned; 1s since creation. 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 EtcdAvailable StatefulSetNotFound 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 Kube APIServer deployment not found 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 [capi-provider deployment has 2 unavailable replicas, cluster-api deployment has 1 unavailable replicas] 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 lookup api.kx-f54a93bc83.zja9.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-09-14 08:46:52 +0000 UTC hostedclusters kx-f54a93bc83 OIDC configuration is valid 2025-09-14 08:46:52 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation completed successfully 2025-09-14 08:47:09 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:47:09 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:47:16 +0000 UTC hostedclusters kx-f54a93bc83 WebIdentityErr 2025-09-14 08:47:38 +0000 UTC hostedclusters kx-f54a93bc83 EtcdAvailable QuorumAvailable 2025-09-14 08:48:41 +0000 UTC hostedclusters kx-f54a93bc83 Kube APIServer deployment is available 2025-09-14 08:48:57 +0000 UTC hostedclusters kx-f54a93bc83 Ignition server deployment is available 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 ClusterVersionSucceeding FromClusterVersion 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Payload loaded version="4.16.47" image="quay.io/openshift-release-dev/ocp-release@sha256:b671a4d6bfd10b567ff593b8488d65d9b5f5a3d642ebb29f3ef294d79992bf9a" architecture="Multi" 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 ClusterVersionAvailable FromClusterVersion 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Working towards 4.16.47: 22 of 624 done (3% complete) 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f54a93bc83 Version 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation active on resource 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Release image is valid 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is supported by operator configuration 2025-09-14 08:45:16 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is at expected version 2025-09-14 08:46:38 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-09-14 08:46:43 +0000 UTC hostedclusters kx-f54a93bc83 Configuration passes validation 2025-09-14 08:46:45 +0000 UTC hostedclusters kx-f54a93bc83 Required platform credentials are found 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 Configuration passes validation 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 AWS KMS is not configured 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 router deployment has 1 unavailable replicas 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 lookup api.kx-f54a93bc83.zja9.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-09-14 08:46:52 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation completed successfully 2025-09-14 08:46:52 +0000 UTC hostedclusters kx-f54a93bc83 OIDC configuration is valid 2025-09-14 08:47:09 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:47:09 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:47:38 +0000 UTC hostedclusters kx-f54a93bc83 EtcdAvailable QuorumAvailable 2025-09-14 08:48:41 +0000 UTC hostedclusters kx-f54a93bc83 Kube APIServer deployment is available 2025-09-14 08:48:57 +0000 UTC hostedclusters kx-f54a93bc83 Ignition server deployment is available 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Payload loaded version="4.16.47" image="quay.io/openshift-release-dev/ocp-release@sha256:b671a4d6bfd10b567ff593b8488d65d9b5f5a3d642ebb29f3ef294d79992bf9a" architecture="Multi" 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 ClusterVersionAvailable FromClusterVersion 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Unable to apply 4.16.47: some cluster operators are not available 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:49:42 +0000 UTC hostedclusters kx-f54a93bc83 Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-09-14 08:49:47 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:49:57 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:49:58 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is available 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f54a93bc83 Version 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation active on resource 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 Release image is valid 2025-09-14 08:45:13 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is supported by operator configuration 2025-09-14 08:45:16 +0000 UTC hostedclusters kx-f54a93bc83 HostedCluster is at expected version 2025-09-14 08:46:38 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-09-14 08:46:43 +0000 UTC hostedclusters kx-f54a93bc83 Configuration passes validation 2025-09-14 08:46:45 +0000 UTC hostedclusters kx-f54a93bc83 Required platform credentials are found 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 Configuration passes validation 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 AWS KMS is not configured 2025-09-14 08:46:47 +0000 UTC hostedclusters kx-f54a93bc83 lookup api.kx-f54a93bc83.zja9.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-09-14 08:46:52 +0000 UTC hostedclusters kx-f54a93bc83 Reconciliation completed successfully 2025-09-14 08:46:52 +0000 UTC hostedclusters kx-f54a93bc83 OIDC configuration is valid 2025-09-14 08:47:09 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:47:09 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:47:38 +0000 UTC hostedclusters kx-f54a93bc83 EtcdAvailable QuorumAvailable 2025-09-14 08:48:41 +0000 UTC hostedclusters kx-f54a93bc83 Kube APIServer deployment is available 2025-09-14 08:48:57 +0000 UTC hostedclusters kx-f54a93bc83 Ignition server deployment is available 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Payload loaded version="4.16.47" image="quay.io/openshift-release-dev/ocp-release@sha256:b671a4d6bfd10b567ff593b8488d65d9b5f5a3d642ebb29f3ef294d79992bf9a" architecture="Multi" 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 ClusterVersionAvailable FromClusterVersion 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Unable to apply 4.16.47: some cluster operators are not available 2025-09-14 08:49:05 +0000 UTC hostedclusters kx-f54a93bc83 Condition not found in the CVO. 2025-09-14 08:49:42 +0000 UTC hostedclusters kx-f54a93bc83 Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-09-14 08:49:47 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:49:57 +0000 UTC hostedclusters kx-f54a93bc83 All is well 2025-09-14 08:50:01 +0000 UTC hostedclusters kx-f54a93bc83 The hosted cluster is not degraded 2025-09-14 08:50:17 +0000 UTC hostedclusters kx-f54a93bc83 The hosted control plane is available INFO: Cluster 'kx-f54a93bc83' is now ready INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster 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.16.47 True False False 3m53s dns 4.16.47 False False True 3m53s DNS "default" is unavailable. image-registry False True True 3m17s Available: The deployment does not have available replicas... ingress False True True 3m37s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.16.47 True False False 3m43s kube-controller-manager 4.16.47 True False False 3m43s kube-scheduler 4.16.47 True False False 3m43s kube-storage-version-migrator monitoring network 4.16.47 True True False 3m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m30s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.47 True False False 3m43s openshift-controller-manager 4.16.47 True False False 3m43s openshift-samples operator-lifecycle-manager 4.16.47 True False False 3m45s operator-lifecycle-manager-catalog 4.16.47 True False False 3m44s operator-lifecycle-manager-packageserver 4.16.47 True False False 3m43s service-ca storage 4.16.47 False False False 3m42s 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.16.47 True False False 3m53s dns 4.16.47 False False True 3m53s DNS "default" is unavailable. image-registry False True True 3m17s Available: The deployment does not have available replicas... ingress False True True 3m37s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.16.47 True False False 3m43s kube-controller-manager 4.16.47 True False False 3m43s kube-scheduler 4.16.47 True False False 3m43s kube-storage-version-migrator monitoring network 4.16.47 True True False 3m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m30s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.47 True False False 3m43s openshift-controller-manager 4.16.47 True False False 3m43s openshift-samples operator-lifecycle-manager 4.16.47 True False False 3m45s operator-lifecycle-manager-catalog 4.16.47 True False False 3m44s operator-lifecycle-manager-packageserver 4.16.47 True False False 3m43s service-ca storage 4.16.47 False False False 3m42s 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.16.47 True False False 4m53s dns 4.16.47 False False True 4m53s DNS "default" is unavailable. image-registry False True True 4m17s Available: The deployment does not have available replicas... ingress False True True 4m37s 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.16.47 True False False 4m43s kube-controller-manager 4.16.47 True False False 4m43s kube-scheduler 4.16.47 True False False 4m43s kube-storage-version-migrator monitoring network 4.16.47 True True False 4m31s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 4m30s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.47 True False False 4m43s openshift-controller-manager 4.16.47 True False False 4m43s openshift-samples operator-lifecycle-manager 4.16.47 True False False 4m45s operator-lifecycle-manager-catalog 4.16.47 True False False 4m44s operator-lifecycle-manager-packageserver 4.16.47 True False False 4m43s service-ca storage 4.16.47 False False False 4m42s 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.16.47 True False False 5m59s dns 4.16.47 False False True 5m59s DNS "default" is unavailable. image-registry False True True 5m23s Available: The deployment does not have available replicas... ingress False True True 5m43s 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.16.47 True False False 5m49s kube-controller-manager 4.16.47 True False False 5m49s kube-scheduler 4.16.47 True False False 5m49s kube-storage-version-migrator monitoring network 4.16.47 True True False 5m37s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 5m36s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.47 True False False 5m49s openshift-controller-manager 4.16.47 True False False 5m49s openshift-samples operator-lifecycle-manager 4.16.47 True False False 5m51s operator-lifecycle-manager-catalog 4.16.47 True False False 5m50s operator-lifecycle-manager-packageserver 4.16.47 True False False 5m49s service-ca storage 4.16.47 False False False 5m48s 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.16.47 True False False 6m59s dns 4.16.47 False False True 6m59s DNS "default" is unavailable. image-registry False True True 6m23s Available: The deployment does not have available replicas... ingress False True True 6m43s 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.16.47 True False False 6m49s kube-controller-manager 4.16.47 True False False 6m49s kube-scheduler 4.16.47 True False False 6m49s kube-storage-version-migrator monitoring network 4.16.47 True True False 6m37s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.16.47 True True False 8s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.16.47 True False False 6m49s openshift-controller-manager 4.16.47 True False False 6m49s openshift-samples operator-lifecycle-manager 4.16.47 True False False 6m51s operator-lifecycle-manager-catalog 4.16.47 True False False 6m50s operator-lifecycle-manager-packageserver 4.16.47 True False False 6m49s service-ca storage 4.16.47 True False False 1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.16.47 True False False 7m59s dns 4.16.47 False True True 7m59s DNS "default" is unavailable. image-registry False True True 7m23s Available: The deployment does not have available replicas... ingress False True True 7m43s 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.16.47 True False False 7m49s kube-controller-manager 4.16.47 True False False 7m49s kube-scheduler 4.16.47 True False False 7m49s kube-storage-version-migrator monitoring network 4.16.47 True True False 7m37s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready node-tuning 4.16.47 True False False 68s openshift-apiserver 4.16.47 True False False 7m49s openshift-controller-manager 4.16.47 True False False 7m49s openshift-samples operator-lifecycle-manager 4.16.47 True False False 7m51s operator-lifecycle-manager-catalog 4.16.47 True False False 7m50s operator-lifecycle-manager-packageserver 4.16.47 True False False 7m49s service-ca storage 4.16.47 True False False 61s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.16.47 True False False 8m59s dns 4.16.47 False True True 8m59s DNS "default" is unavailable. image-registry False True True 8m23s Available: The deployment does not have available replicas... ingress False True True 8m43s 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.16.47 True False False 10s kube-apiserver 4.16.47 True False False 8m49s kube-controller-manager 4.16.47 True False False 8m49s kube-scheduler 4.16.47 True False False 8m49s kube-storage-version-migrator 4.16.47 False True False 9s KubeStorageVersionMigratorAvailable: Waiting for Deployment monitoring network 4.16.47 True True False 8m37s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready node-tuning 4.16.47 True False False 2m8s openshift-apiserver 4.16.47 True False False 8m49s openshift-controller-manager 4.16.47 True False False 8m49s openshift-samples operator-lifecycle-manager 4.16.47 True False False 8m51s operator-lifecycle-manager-catalog 4.16.47 True False False 8m50s operator-lifecycle-manager-packageserver 4.16.47 True False False 8m49s service-ca True True False 8s Progressing: ... storage 4.16.47 True False False 2m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True True False 16s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 9m59s dns 4.16.47 True False False 28s image-registry True True False 19s Progressing: The deployment has not completed... ingress 4.16.47 True True True 11s 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.16.47 True False False 70s kube-apiserver 4.16.47 True False False 9m49s kube-controller-manager 4.16.47 True False False 9m49s kube-scheduler 4.16.47 True False False 9m49s kube-storage-version-migrator 4.16.47 True False False 46s monitoring Unknown True Unknown 56s Rolling out the stack. network 4.16.47 True True False 9m37s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready node-tuning 4.16.47 True False False 3m8s openshift-apiserver 4.16.47 True False False 9m49s openshift-controller-manager 4.16.47 True False False 9m49s openshift-samples 4.16.47 True False False 24s operator-lifecycle-manager 4.16.47 True False False 9m51s operator-lifecycle-manager-catalog 4.16.47 True False False 9m50s operator-lifecycle-manager-packageserver 4.16.47 True False False 9m49s service-ca 4.16.47 True False False 68s storage 4.16.47 True False False 3m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True True False 77s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 11m dns 4.16.47 True False False 89s image-registry True True True 80s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5c99698486" has timed out progressing. ingress 4.16.47 True True False 72s 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.16.47 True False False 2m11s kube-apiserver 4.16.47 True False False 10m kube-controller-manager 4.16.47 True False False 10m kube-scheduler 4.16.47 True False False 10m kube-storage-version-migrator 4.16.47 True False False 107s monitoring Unknown True Unknown 117s Rolling out the stack. network 4.16.47 True False False 10m node-tuning 4.16.47 True False False 4m9s openshift-apiserver 4.16.47 True False False 10m openshift-controller-manager 4.16.47 True False False 10m openshift-samples 4.16.47 True False False 85s operator-lifecycle-manager 4.16.47 True False False 10m operator-lifecycle-manager-catalog 4.16.47 True False False 10m operator-lifecycle-manager-packageserver 4.16.47 True False False 10m service-ca 4.16.47 True False False 2m9s storage 4.16.47 True False False 4m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True True False 2m17s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 12m dns 4.16.47 True False False 2m29s image-registry True True True 2m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5c99698486" has timed out progressing. ingress 4.16.47 True True False 2m12s 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.16.47 True False False 3m11s kube-apiserver 4.16.47 True False False 11m kube-controller-manager 4.16.47 True False False 11m kube-scheduler 4.16.47 True False False 11m kube-storage-version-migrator 4.16.47 True False False 2m47s monitoring Unknown True Unknown 2m57s Rolling out the stack. network 4.16.47 True False False 11m node-tuning 4.16.47 True False False 5m9s openshift-apiserver 4.16.47 True False False 11m openshift-controller-manager 4.16.47 True False False 11m openshift-samples 4.16.47 True False False 2m25s operator-lifecycle-manager 4.16.47 True False False 11m operator-lifecycle-manager-catalog 4.16.47 True False False 11m operator-lifecycle-manager-packageserver 4.16.47 True False False 11m service-ca 4.16.47 True False False 3m9s storage 4.16.47 True False False 5m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True True False 3m17s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 13m dns 4.16.47 True False False 3m29s image-registry True True True 3m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5c99698486" has timed out progressing. ingress 4.16.47 True True False 3m12s 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.16.47 True False False 4m11s kube-apiserver 4.16.47 True False False 12m kube-controller-manager 4.16.47 True False False 12m kube-scheduler 4.16.47 True False False 12m kube-storage-version-migrator 4.16.47 True False False 3m47s monitoring Unknown True Unknown 3m57s Rolling out the stack. network 4.16.47 True False False 12m node-tuning 4.16.47 True False False 6m9s openshift-apiserver 4.16.47 True False False 12m openshift-controller-manager 4.16.47 True False False 12m openshift-samples 4.16.47 True False False 3m25s operator-lifecycle-manager 4.16.47 True False False 12m operator-lifecycle-manager-catalog 4.16.47 True False False 12m operator-lifecycle-manager-packageserver 4.16.47 True False False 12m service-ca 4.16.47 True False False 4m9s storage 4.16.47 True False False 6m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True True False 4m17s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 14m dns 4.16.47 True False False 4m29s image-registry True True True 4m20s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5c99698486" has timed out progressing. ingress 4.16.47 True True False 4m12s 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.16.47 True False False 5m11s kube-apiserver 4.16.47 True False False 13m kube-controller-manager 4.16.47 True False False 13m kube-scheduler 4.16.47 True False False 13m kube-storage-version-migrator 4.16.47 True False False 4m47s monitoring Unknown True Unknown 4m57s Rolling out the stack. network 4.16.47 True False False 13m node-tuning 4.16.47 True False False 7m9s openshift-apiserver 4.16.47 True False False 13m openshift-controller-manager 4.16.47 True False False 13m openshift-samples 4.16.47 True False False 4m25s operator-lifecycle-manager 4.16.47 True False False 13m operator-lifecycle-manager-catalog 4.16.47 True False False 13m operator-lifecycle-manager-packageserver 4.16.47 True False False 13m service-ca 4.16.47 True False False 5m9s storage 4.16.47 True False False 7m2s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True True False 5m18s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 15m dns 4.16.47 True True False 5m30s DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2." image-registry True True True 5m21s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5c99698486" has timed out progressing. ingress 4.16.47 True True False 5m13s 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.16.47 True False False 6m12s kube-apiserver 4.16.47 True False False 14m kube-controller-manager 4.16.47 True False False 14m kube-scheduler 4.16.47 True False False 14m kube-storage-version-migrator 4.16.47 True False False 5m48s monitoring Unknown True Unknown 5m58s Rolling out the stack. network 4.16.47 True True False 14m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.16.47 True True False 41s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.47 True False False 14m openshift-controller-manager 4.16.47 True False False 14m openshift-samples 4.16.47 True False False 5m26s operator-lifecycle-manager 4.16.47 True False False 14m operator-lifecycle-manager-catalog 4.16.47 True False False 14m operator-lifecycle-manager-packageserver 4.16.47 True False False 14m service-ca 4.16.47 True False False 6m10s storage 4.16.47 True True False 8m3s 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.16.47 True True False 6m18s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 16m dns 4.16.47 True False False 6m30s image-registry True True True 6m21s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-5c99698486" has timed out progressing. ingress 4.16.47 True True False 6m13s 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.16.47 True False False 7m12s kube-apiserver 4.16.47 True False False 15m kube-controller-manager 4.16.47 True False False 15m kube-scheduler 4.16.47 True False False 15m kube-storage-version-migrator 4.16.47 True False False 6m48s monitoring Unknown True Unknown 6m58s Rolling out the stack. network 4.16.47 True False False 15m node-tuning 4.16.47 True False False 101s openshift-apiserver 4.16.47 True False False 15m openshift-controller-manager 4.16.47 True False False 15m openshift-samples 4.16.47 True False False 6m26s operator-lifecycle-manager 4.16.47 True False False 15m operator-lifecycle-manager-catalog 4.16.47 True False False 15m operator-lifecycle-manager-packageserver 4.16.47 True False False 15m service-ca 4.16.47 True False False 7m10s storage 4.16.47 True False False 9m3s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.47 True False False 7m18s csi-snapshot-controller 4.16.47 True False False 17m dns 4.16.47 True False False 7m30s image-registry 4.16.47 True True False 7m21s Progressing: The deployment has not completed... ingress 4.16.47 True False False 7m13s insights 4.16.47 True False False 8m12s kube-apiserver 4.16.47 True False False 16m kube-controller-manager 4.16.47 True False False 16m kube-scheduler 4.16.47 True False False 16m kube-storage-version-migrator 4.16.47 True False False 7m48s monitoring Unknown True Unknown 7m58s Rolling out the stack. network 4.16.47 True False False 16m node-tuning 4.16.47 True False False 2m41s openshift-apiserver 4.16.47 True False False 16m openshift-controller-manager 4.16.47 True False False 16m openshift-samples 4.16.47 True False False 7m26s operator-lifecycle-manager 4.16.47 True False False 16m operator-lifecycle-manager-catalog 4.16.47 True False False 16m operator-lifecycle-manager-packageserver 4.16.47 True False False 16m service-ca 4.16.47 True False False 8m10s storage 4.16.47 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.16.47 True False False 8m18s csi-snapshot-controller 4.16.47 True False False 18m dns 4.16.47 True False False 8m30s image-registry 4.16.47 True False False 8m21s ingress 4.16.47 True False False 8m13s insights 4.16.47 True False False 9m12s kube-apiserver 4.16.47 True False False 17m kube-controller-manager 4.16.47 True False False 17m kube-scheduler 4.16.47 True False False 17m kube-storage-version-migrator 4.16.47 True False False 8m48s monitoring Unknown True Unknown 8m58s Rolling out the stack. network 4.16.47 True False False 17m node-tuning 4.16.47 True False False 3m41s openshift-apiserver 4.16.47 True False False 17m openshift-controller-manager 4.16.47 True False False 17m openshift-samples 4.16.47 True False False 8m26s operator-lifecycle-manager 4.16.47 True False False 17m operator-lifecycle-manager-catalog 4.16.47 True False False 17m operator-lifecycle-manager-packageserver 4.16.47 True False False 17m service-ca 4.16.47 True False False 9m10s storage 4.16.47 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.16.47 True True False 9m19s SyncLoopRefreshProgressing: working toward version 4.16.47, 1 replicas available csi-snapshot-controller 4.16.47 True False False 19m dns 4.16.47 True True False 9m31s DNS "default" reports Progressing=True: "Have 2 available node-resolver pods, want 3." image-registry 4.16.47 True True False 9m22s Progressing: The registry is ready... ingress 4.16.47 True False False 9m14s insights 4.16.47 True False False 10m kube-apiserver 4.16.47 True False False 18m kube-controller-manager 4.16.47 True False False 18m kube-scheduler 4.16.47 True False False 18m kube-storage-version-migrator 4.16.47 True False False 9m49s monitoring 4.16.47 True False False 47s network 4.16.47 True True False 18m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.16.47 True True False 5s Waiting for 1/3 Profiles to be applied openshift-apiserver 4.16.47 True False False 18m openshift-controller-manager 4.16.47 True False False 18m openshift-samples 4.16.47 True False False 9m27s operator-lifecycle-manager 4.16.47 True False False 18m operator-lifecycle-manager-catalog 4.16.47 True False False 18m operator-lifecycle-manager-packageserver 4.16.47 True False False 18m service-ca 4.16.47 True False False 10m storage 4.16.47 True True False 12m 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.16.47 True False False 10m csi-snapshot-controller 4.16.47 True False False 20m dns 4.16.47 True False False 10m image-registry 4.16.47 True False False 10m ingress 4.16.47 True False False 10m insights 4.16.47 True False False 11m kube-apiserver 4.16.47 True False False 19m kube-controller-manager 4.16.47 True False False 19m kube-scheduler 4.16.47 True False False 19m kube-storage-version-migrator 4.16.47 True False False 10m monitoring 4.16.47 True False False 107s network 4.16.47 True False False 19m node-tuning 4.16.47 True False False 65s openshift-apiserver 4.16.47 True False False 19m openshift-controller-manager 4.16.47 True False False 19m openshift-samples 4.16.47 True False False 10m operator-lifecycle-manager 4.16.47 True False False 19m operator-lifecycle-manager-catalog 4.16.47 True False False 19m operator-lifecycle-manager-packageserver 4.16.47 True False False 19m service-ca 4.16.47 True False False 11m storage 4.16.47 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.16.47 True False False 11m csi-snapshot-controller 4.16.47 True False False 21m dns 4.16.47 True False False 11m image-registry 4.16.47 True False False 11m ingress 4.16.47 True False False 11m insights 4.16.47 True False False 12m kube-apiserver 4.16.47 True False False 20m kube-controller-manager 4.16.47 True False False 20m kube-scheduler 4.16.47 True False False 20m kube-storage-version-migrator 4.16.47 True False False 11m monitoring 4.16.47 True False False 2m47s network 4.16.47 True False False 20m node-tuning 4.16.47 True False False 2m5s openshift-apiserver 4.16.47 True False False 20m openshift-controller-manager 4.16.47 True False False 20m openshift-samples 4.16.47 True False False 11m operator-lifecycle-manager 4.16.47 True False False 20m operator-lifecycle-manager-catalog 4.16.47 True False False 20m operator-lifecycle-manager-packageserver 4.16.47 True False False 20m service-ca 4.16.47 True False False 12m storage 4.16.47 True False False 14m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!