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.59). 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.59). WARN: It is recommended that you update to the latest version. INFO: Creating cluster 'kx-3ddc3d5199' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-3ddc3d5199' 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-3ddc3d5199 Domain Prefix: kx-3ddc3d5199 Display Name: kx-3ddc3d5199 ID: 2nb8omls90p13j4mqhm7ts2i1jpihjlc External ID: 12e96000-c8cc-4f2a-a175-30f4bbd1e8ef Control Plane: ROSA Service Hosted OpenShift Version: 4.19.9 Channel Group: stable DNS: Not ready AWS Account: 381492310364 AWS Billing Account: 381492310364 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-0208a6297964e4fe1, subnet-0c161c939f7025e15, subnet-023e5c7b3016ed194, subnet-02dbd8abbf884d77f, subnet-0360c2d20442c5ba5, subnet-0aad9c992e402a91a EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::381492310364:role/rhads-hcp-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 - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-kube-controller-manager - arn:aws:iam::381492310364:role/rhads-hcp-kube-system-capa-controller-manager Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Dec 22 2025 05:42:53 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/37Bh3b2vfsj3KkI7GOo59lCN8ns 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-3ddc3d5199'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-3ddc3d5199 --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.59). 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-3ddc3d5199' 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-3ddc3d5199 Version 2025-12-22 05:48:12 +0000 UTC hostedclusters kx-3ddc3d5199 ValidAWSIdentityProvider StatusUnknown 2025-12-22 05:48:13 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-12-22 05:48:13 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 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-3ddc3d5199 Version 2025-12-22 05:48:12 +0000 UTC hostedclusters kx-3ddc3d5199 ValidAWSIdentityProvider StatusUnknown 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Release image is valid 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the HCP 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is at expected version 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation active on resource 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment not found 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 HostedCluster is supported by operator configuration 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-04103195f534ae37c', 'i-0018c6fa70864b957'\n\tstatus code: 400, request id: 623501ec-6834-4083-887d-93f307f3ad01"; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-04103195f534ae37c', 'i-0018c6fa70864b957'\n\tstatus code: 400, request id: 623501ec-6834-4083-887d-93f307f3ad01" 2025-12-22 05:48:15 +0000 UTC hostedclusters kx-3ddc3d5199 Condition not found in the CVO. 2025-12-22 05:49:40 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-12-22 05:49:45 +0000 UTC hostedclusters kx-3ddc3d5199 Configuration passes validation 2025-12-22 05:49:47 +0000 UTC hostedclusters kx-3ddc3d5199 Required platform credentials are found 2025-12-22 05:49:49 +0000 UTC hostedclusters kx-3ddc3d5199 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-04103195f534ae37c', 'i-0018c6fa70864b957'\n\tstatus code: 400, request id: 623501ec-6834-4083-887d-93f307f3ad01"; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-04103195f534ae37c', 'i-0018c6fa70864b957'\n\tstatus code: 400, request id: 623501ec-6834-4083-887d-93f307f3ad01" 2025-12-22 05:49:49 +0000 UTC hostedclusters kx-3ddc3d5199 lookup api.kx-3ddc3d5199.7ag9.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-12-22 05:49:49 +0000 UTC hostedclusters kx-3ddc3d5199 Configuration passes validation 2025-12-22 05:49:49 +0000 UTC hostedclusters kx-3ddc3d5199 AWS KMS is not configured 2025-12-22 05:49:49 +0000 UTC hostedclusters kx-3ddc3d5199 EtcdAvailable StatefulSetNotFound 2025-12-22 05:49:49 +0000 UTC hostedclusters kx-3ddc3d5199 Kube APIServer deployment not found 2025-12-22 05:49:50 +0000 UTC hostedclusters kx-3ddc3d5199 capi-provider deployment has 1 unavailable replicas 2025-12-22 05:49:53 +0000 UTC hostedclusters kx-3ddc3d5199 OIDC configuration is valid 2025-12-22 05:49:53 +0000 UTC hostedclusters kx-3ddc3d5199 Reconciliation completed successfully 2025-12-22 05:50:18 +0000 UTC hostedclusters kx-3ddc3d5199 WebIdentityErr 2025-12-22 05:52:49 +0000 UTC hostedclusters kx-3ddc3d5199 All is well 2025-12-22 05:52:49 +0000 UTC hostedclusters kx-3ddc3d5199 All is well 2025-12-22 05:52:49 +0000 UTC hostedclusters kx-3ddc3d5199 All is well 2025-12-22 05:52:49 +0000 UTC hostedclusters kx-3ddc3d5199 All is well 2025-12-22 05:53:16 +0000 UTC hostedclusters kx-3ddc3d5199 EtcdAvailable QuorumAvailable 2025-12-22 05:53:50 +0000 UTC hostedclusters kx-3ddc3d5199 Kube APIServer deployment is available 2025-12-22 05:54:07 +0000 UTC hostedclusters kx-3ddc3d5199 Ignition server deployment is available 2025-12-22 05:54:15 +0000 UTC hostedclusters kx-3ddc3d5199 The hosted control plane is available INFO: Cluster 'kx-3ddc3d5199' 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.59). WARN: It is recommended that you update to the latest version. INFO: Storing login command... INFO: Check if it's able to login to OCP cluster... Retried 1 times... INFO: Check if apiserver is ready... Waiting for cluster operators to be accessible for 2m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 111s dns 4.19.9 False False True 109s DNS "default" is unavailable. image-registry False True True 92s NodeCADaemonAvailable: The daemon set node-ca does not have available replicas... ingress False True True 90s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 98s kube-controller-manager 4.19.9 True False False 98s kube-scheduler 4.19.9 True False False 98s kube-storage-version-migrator monitoring network 4.19.9 True True False 81s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 97s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 98s openshift-controller-manager 4.19.9 True False False 98s openshift-samples operator-lifecycle-manager 4.19.9 True False False 99s operator-lifecycle-manager-catalog 4.19.9 True False False 92s operator-lifecycle-manager-packageserver 4.19.9 True False False 98s service-ca storage 4.19.9 False False False 97s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service cluster operators to be accessible finished! [INFO] Cluster operators are accessible. Waiting for cluster to be reported as healthy for 60m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 111s dns 4.19.9 False False True 109s DNS "default" is unavailable. image-registry False True True 92s NodeCADaemonAvailable: The daemon set node-ca does not have available replicas... ingress False True True 90s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 98s kube-controller-manager 4.19.9 True False False 98s kube-scheduler 4.19.9 True False False 98s kube-storage-version-migrator monitoring network 4.19.9 True True False 81s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 97s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 98s openshift-controller-manager 4.19.9 True False False 98s openshift-samples operator-lifecycle-manager 4.19.9 True False False 99s operator-lifecycle-manager-catalog 4.19.9 True False False 92s operator-lifecycle-manager-packageserver 4.19.9 True False False 98s service-ca storage 4.19.9 False False False 97s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 2m51s dns 4.19.9 False False True 2m49s DNS "default" is unavailable. image-registry False True True 2m32s NodeCADaemonAvailable: The daemon set node-ca does not have available replicas... ingress False True True 2m30s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 2m38s kube-controller-manager 4.19.9 True False False 2m38s kube-scheduler 4.19.9 True False False 2m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 2m21s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 2m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 2m38s openshift-controller-manager 4.19.9 True False False 2m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 2m39s operator-lifecycle-manager-catalog 4.19.9 True False False 2m32s operator-lifecycle-manager-packageserver 4.19.9 True False False 2m38s service-ca storage 4.19.9 False False False 2m37s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 3m51s dns 4.19.9 False False True 3m49s DNS "default" is unavailable. image-registry False True True 3m32s NodeCADaemonAvailable: The daemon set node-ca does not have available replicas... ingress False True True 3m30s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 3m38s kube-controller-manager 4.19.9 True False False 3m38s kube-scheduler 4.19.9 True False False 3m38s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m21s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 3m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 3m38s openshift-controller-manager 4.19.9 True False False 3m38s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m39s operator-lifecycle-manager-catalog 4.19.9 True False False 3m32s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m38s service-ca storage 4.19.9 False False False 3m37s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 4m52s dns 4.19.9 False False True 4m50s DNS "default" is unavailable. image-registry False True True 4m33s NodeCADaemonAvailable: The daemon set node-ca does not have available replicas... ingress False True True 4m31s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 4m39s kube-controller-manager 4.19.9 True False False 4m39s kube-scheduler 4.19.9 True False False 4m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m22s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 4m38s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 4m39s openshift-controller-manager 4.19.9 True False False 4m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m40s operator-lifecycle-manager-catalog 4.19.9 True False False 4m33s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m39s service-ca storage 4.19.9 False False False 4m38s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 5m52s dns 4.19.9 False True True 5m50s DNS "default" is unavailable. image-registry False True True 5m33s NodeCADaemonAvailable: The daemon set node-ca has available replicas... ingress False True True 5m31s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 5m39s kube-controller-manager 4.19.9 True False False 5m39s kube-scheduler 4.19.9 True False False 5m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m22s DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 4s Waiting for 3/3 Profiles to be applied openshift-apiserver 4.19.9 True False False 5m39s openshift-controller-manager 4.19.9 True False False 5m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m40s operator-lifecycle-manager-catalog 4.19.9 True False False 5m33s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m39s service-ca storage 4.19.9 True True False 15s 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 csi-snapshot-controller 4.19.9 True False False 6m52s dns 4.19.9 False False True 6m50s DNS "default" is unavailable. image-registry False True True 6m33s NodeCADaemonAvailable: The daemon set node-ca has available replicas... ingress False True True 6m31s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.19.9 True False False 6m39s kube-controller-manager 4.19.9 True False False 6m39s kube-scheduler 4.19.9 True False False 6m39s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m22s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes)... node-tuning 4.19.9 True False False 64s openshift-apiserver 4.19.9 True False False 6m39s openshift-controller-manager 4.19.9 True False False 6m39s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m40s operator-lifecycle-manager-catalog 4.19.9 True False False 6m33s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m39s service-ca storage 4.19.9 True False False 75s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 0s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 7m52s dns 4.19.9 True True False 7s DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3." image-registry True True False 2s NodeCADaemonProgressing: The daemon set node-ca is deployed... ingress False True True 7m31s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.19.9 True False False 40s kube-apiserver 4.19.9 True False False 7m39s kube-controller-manager 4.19.9 True False False 7m39s kube-scheduler 4.19.9 True False False 7m39s kube-storage-version-migrator 4.19.9 True False False 37s monitoring Unknown True Unknown 9s Rolling out the stack. network 4.19.9 True True False 7m22s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes) node-tuning 4.19.9 True False False 2m4s openshift-apiserver 4.19.9 True False False 7m39s openshift-controller-manager 4.19.9 True False False 7m39s openshift-samples False False False 3s SampleUpsertsPending operator-lifecycle-manager 4.19.9 True False False 7m40s operator-lifecycle-manager-catalog 4.19.9 True False False 7m33s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m39s service-ca 4.19.9 True False False 39s storage 4.19.9 True False False 2m15s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True False False 61s csi-snapshot-controller 4.19.9 True False False 8m53s dns 4.19.9 True False False 68s image-registry 4.19.9 True False False 63s ingress 4.19.9 True False False 41s insights 4.19.9 True False False 101s kube-apiserver 4.19.9 True False False 8m40s kube-controller-manager 4.19.9 True False False 8m40s kube-scheduler 4.19.9 True False False 8m40s kube-storage-version-migrator 4.19.9 True False False 98s monitoring Unknown True Unknown 70s Rolling out the stack. network 4.19.9 True True False 8m23s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.19.9 True False False 3m5s openshift-apiserver 4.19.9 True False False 8m40s openshift-controller-manager 4.19.9 True False False 8m40s openshift-samples 4.19.9 True False False 54s operator-lifecycle-manager 4.19.9 True False False 8m41s operator-lifecycle-manager-catalog 4.19.9 True False False 8m34s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m40s service-ca 4.19.9 True False False 100s storage 4.19.9 True False False 3m16s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True True False 2m1s SyncLoopRefreshProgressing: working toward version 4.19.9, 1 replicas available csi-snapshot-controller 4.19.9 True False False 9m53s dns 4.19.9 True False False 2m8s image-registry 4.19.9 True False False 2m3s ingress 4.19.9 True False False 101s insights 4.19.9 True False False 2m41s kube-apiserver 4.19.9 True False False 9m40s kube-controller-manager 4.19.9 True False False 9m40s kube-scheduler 4.19.9 True False False 9m40s kube-storage-version-migrator 4.19.9 True False False 2m38s monitoring Unknown True Unknown 2m10s Rolling out the stack. network 4.19.9 True False False 9m23s node-tuning 4.19.9 True False False 4m5s openshift-apiserver 4.19.9 True False False 9m40s openshift-controller-manager 4.19.9 True False False 9m40s openshift-samples 4.19.9 True False False 114s operator-lifecycle-manager 4.19.9 True False False 9m41s operator-lifecycle-manager-catalog 4.19.9 True False False 9m34s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m40s service-ca 4.19.9 True False False 2m40s storage 4.19.9 True False False 4m16s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.19.9 True False False 3m1s csi-snapshot-controller 4.19.9 True False False 10m dns 4.19.9 True False False 3m8s image-registry 4.19.9 True False False 3m3s ingress 4.19.9 True False False 2m41s insights 4.19.9 True False False 3m41s kube-apiserver 4.19.9 True False False 10m kube-controller-manager 4.19.9 True False False 10m kube-scheduler 4.19.9 True False False 10m kube-storage-version-migrator 4.19.9 True False False 3m38s monitoring 4.19.9 True False False 55s network 4.19.9 True False False 10m node-tuning 4.19.9 True False False 5m5s openshift-apiserver 4.19.9 True False False 10m openshift-controller-manager 4.19.9 True False False 10m openshift-samples 4.19.9 True False False 2m54s operator-lifecycle-manager 4.19.9 True False False 10m operator-lifecycle-manager-catalog 4.19.9 True False False 10m operator-lifecycle-manager-packageserver 4.19.9 True False False 10m service-ca 4.19.9 True False False 3m40s storage 4.19.9 True False False 5m16s Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!