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-fc3e652ae2' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-fc3e652ae2' 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-fc3e652ae2 Domain Prefix: kx-fc3e652ae2 Display Name: kx-fc3e652ae2 ID: 2m2psefvoihcavplkdb8dofvta743vr6 External ID: ab1fa407-535a-4150-ac66-4a02c1d5ec64 Control Plane: ROSA Service Hosted OpenShift Version: 4.19.9 Channel Group: stable DNS: Not ready AWS Account: 381492310364 AWS Billing Account: 381492310364 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-0208a6297964e4fe1, subnet-0c161c939f7025e15, subnet-023e5c7b3016ed194, subnet-02dbd8abbf884d77f, subnet-0360c2d20442c5ba5, subnet-0aad9c992e402a91a EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::381492310364:role/rhads-hcp-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::381492310364:role/rhads-hcp-openshift-cloud-network-config-controller-cloud-creden - 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-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-cluster-csi-drivers-ebs-cloud-credentials Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 21 2025 20:25:33 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34OIkIXuTVTRw9BFUE1tcF3ahwU 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-fc3e652ae2'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-fc3e652ae2 --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-fc3e652ae2' 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-fc3e652ae2 Version 2025-10-21 20:30:17 +0000 UTC hostedclusters kx-fc3e652ae2 ValidAWSIdentityProvider StatusUnknown 2025-10-21 20:30:18 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-21 20:30:18 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Ignition server deployment not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 HostedCluster is supported by operator configuration 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Release image is valid 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Reconciliation active on resource 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is not found 2025-10-21 20:30:22 +0000 UTC hostedclusters kx-fc3e652ae2 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-21 20:30:22 +0000 UTC hostedclusters kx-fc3e652ae2 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-fc3e652ae2 Version 2025-10-21 20:30:17 +0000 UTC hostedclusters kx-fc3e652ae2 ValidAWSIdentityProvider StatusUnknown 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Release image is valid 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the HCP 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Reconciliation active on resource 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Ignition server deployment not found 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 HostedCluster is supported by operator configuration 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-053e8be4e6f2aab9b'\\n\\tstatus code: 400, request id: f7674286-ab5a-41fe-9d45-d570cbdae8e8\""; private-router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-053e8be4e6f2aab9b'\\n\\tstatus code: 400, request id: 44101f1a-62c6-4f16-b40a-5a355884cbe8\""; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-053e8be4e6f2aab9b'\\n\\tstatus code: 400, request id: f7674286-ab5a-41fe-9d45-d570cbdae8e8\"" 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:21 +0000 UTC hostedclusters kx-fc3e652ae2 Condition not found in the CVO. 2025-10-21 20:30:22 +0000 UTC hostedclusters kx-fc3e652ae2 HostedCluster is at expected version 2025-10-21 20:31:48 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-21 20:31:53 +0000 UTC hostedclusters kx-fc3e652ae2 Configuration passes validation 2025-10-21 20:31:54 +0000 UTC hostedclusters kx-fc3e652ae2 Required platform credentials are found 2025-10-21 20:31:57 +0000 UTC hostedclusters kx-fc3e652ae2 Configuration passes validation 2025-10-21 20:31:57 +0000 UTC hostedclusters kx-fc3e652ae2 AWS KMS is not configured 2025-10-21 20:31:57 +0000 UTC hostedclusters kx-fc3e652ae2 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-053e8be4e6f2aab9b'\\n\\tstatus code: 400, request id: f7674286-ab5a-41fe-9d45-d570cbdae8e8\""; private-router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-053e8be4e6f2aab9b'\\n\\tstatus code: 400, request id: 44101f1a-62c6-4f16-b40a-5a355884cbe8\""; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-053e8be4e6f2aab9b'\\n\\tstatus code: 400, request id: f7674286-ab5a-41fe-9d45-d570cbdae8e8\"" 2025-10-21 20:31:57 +0000 UTC hostedclusters kx-fc3e652ae2 EtcdAvailable StatefulSetNotFound 2025-10-21 20:31:57 +0000 UTC hostedclusters kx-fc3e652ae2 Kube APIServer deployment not found 2025-10-21 20:31:57 +0000 UTC hostedclusters kx-fc3e652ae2 lookup api.kx-fc3e652ae2.f8c9.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-21 20:31:58 +0000 UTC hostedclusters kx-fc3e652ae2 capi-provider deployment has 2 unavailable replicas 2025-10-21 20:31:59 +0000 UTC hostedclusters kx-fc3e652ae2 OIDC configuration is valid 2025-10-21 20:31:59 +0000 UTC hostedclusters kx-fc3e652ae2 Reconciliation completed successfully 2025-10-21 20:32:26 +0000 UTC hostedclusters kx-fc3e652ae2 WebIdentityErr 2025-10-21 20:33:25 +0000 UTC hostedclusters kx-fc3e652ae2 All is well 2025-10-21 20:33:42 +0000 UTC hostedclusters kx-fc3e652ae2 All is well 2025-10-21 20:34:13 +0000 UTC hostedclusters kx-fc3e652ae2 EtcdAvailable QuorumAvailable 2025-10-21 20:34:55 +0000 UTC hostedclusters kx-fc3e652ae2 Kube APIServer deployment is available 2025-10-21 20:35:25 +0000 UTC hostedclusters kx-fc3e652ae2 Ignition server deployment is available 2025-10-21 20:35:26 +0000 UTC hostedclusters kx-fc3e652ae2 All is well 2025-10-21 20:35:28 +0000 UTC hostedclusters kx-fc3e652ae2 All is well 2025-10-21 20:35:28 +0000 UTC hostedclusters kx-fc3e652ae2 The hosted control plane is available INFO: Cluster 'kx-fc3e652ae2' is now ready INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster WARN: The current version (1.2.56) is not up to date with latest rosa cli released version (1.2.57). WARN: It is recommended that you update to the latest version. INFO: Storing login command... INFO: Check if it's able to login to OCP cluster... Retried 1 times... INFO: Check if apiserver is ready... Waiting for cluster operators to be accessible for 2m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.19.9 True False False 2m19s dns 4.19.9 False False True 2m19s DNS "default" is unavailable. image-registry False True True 81s Available: The deployment does not have available replicas... ingress False True True 119s 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 2m7s kube-controller-manager 4.19.9 True False False 2m7s kube-scheduler 4.19.9 True False False 2m7s kube-storage-version-migrator monitoring network 4.19.9 True True False 113s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 95s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 2m7s openshift-controller-manager 4.19.9 True False False 2m7s openshift-samples operator-lifecycle-manager 4.19.9 True False False 2m12s operator-lifecycle-manager-catalog 4.19.9 True False False 2m8s operator-lifecycle-manager-packageserver 4.19.9 True False False 2m7s service-ca storage 4.19.9 False False False 2m7s 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 2m20s dns 4.19.9 False False True 2m20s DNS "default" is unavailable. image-registry False True True 82s Available: The deployment does not have available replicas... ingress False True True 2m 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 2m8s kube-controller-manager 4.19.9 True False False 2m8s kube-scheduler 4.19.9 True False False 2m8s kube-storage-version-migrator monitoring network 4.19.9 True True False 114s Deployment "/openshift-network-console/networking-console-plugin" is not available (awaiting 2 nodes) node-tuning False True False 96s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 2m8s openshift-controller-manager 4.19.9 True False False 2m8s openshift-samples operator-lifecycle-manager 4.19.9 True False False 2m13s operator-lifecycle-manager-catalog 4.19.9 True False False 2m9s operator-lifecycle-manager-packageserver 4.19.9 True False False 2m8s service-ca storage 4.19.9 False False False 2m8s 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 3m21s dns 4.19.9 False False True 3m21s DNS "default" is unavailable. image-registry False True True 2m23s Available: The deployment does not have available replicas... ingress False True True 3m1s 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 3m9s kube-controller-manager 4.19.9 True False False 3m9s kube-scheduler 4.19.9 True False False 3m9s kube-storage-version-migrator monitoring network 4.19.9 True True False 2m55s 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 3m9s openshift-controller-manager 4.19.9 True False False 3m9s openshift-samples operator-lifecycle-manager 4.19.9 True False False 3m14s operator-lifecycle-manager-catalog 4.19.9 True False False 3m10s operator-lifecycle-manager-packageserver 4.19.9 True False False 3m9s service-ca storage 4.19.9 False False False 3m9s 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 4m21s dns 4.19.9 False False True 4m21s DNS "default" is unavailable. image-registry False True True 3m23s Available: The deployment does not have available replicas... ingress False True True 4m1s 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 4m9s kube-controller-manager 4.19.9 True False False 4m9s kube-scheduler 4.19.9 True False False 4m9s kube-storage-version-migrator monitoring network 4.19.9 True True False 3m55s 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 4m9s openshift-controller-manager 4.19.9 True False False 4m9s openshift-samples operator-lifecycle-manager 4.19.9 True False False 4m14s operator-lifecycle-manager-catalog 4.19.9 True False False 4m10s operator-lifecycle-manager-packageserver 4.19.9 True False False 4m9s service-ca storage 4.19.9 False False False 4m9s 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 5m21s dns 4.19.9 False True True 5m21s DNS "default" is unavailable. image-registry False True True 4m23s Available: The deployment does not have available replicas... ingress False True True 5m1s 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 5m9s kube-controller-manager 4.19.9 True False False 5m9s kube-scheduler 4.19.9 True False False 5m9s kube-storage-version-migrator monitoring network 4.19.9 True True False 4m55s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning False True False 4m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.19.9 True False False 5m9s openshift-controller-manager 4.19.9 True False False 5m9s openshift-samples operator-lifecycle-manager 4.19.9 True False False 5m14s operator-lifecycle-manager-catalog 4.19.9 True False False 5m10s operator-lifecycle-manager-packageserver 4.19.9 True False False 5m9s service-ca storage 4.19.9 False True False 5m9s 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 6m22s dns 4.19.9 False False True 6m22s DNS "default" is unavailable. image-registry False True True 5m24s Available: The deployment does not have available replicas... ingress False True True 6m2s 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 6m10s kube-controller-manager 4.19.9 True False False 6m10s kube-scheduler 4.19.9 True False False 6m10s kube-storage-version-migrator monitoring network 4.19.9 True True False 5m56s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)... node-tuning 4.19.9 True False False 42s openshift-apiserver 4.19.9 True False False 6m10s openshift-controller-manager 4.19.9 True False False 6m10s openshift-samples operator-lifecycle-manager 4.19.9 True False False 6m15s operator-lifecycle-manager-catalog 4.19.9 True False False 6m11s operator-lifecycle-manager-packageserver 4.19.9 True False False 6m10s service-ca storage 4.19.9 True False False 36s 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 7m22s dns 4.19.9 False True True 7m22s DNS "default" is unavailable. image-registry False True True 6m24s Available: The deployment does not have available replicas... ingress False True True 7m2s 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 7m10s kube-controller-manager 4.19.9 True False False 7m10s kube-scheduler 4.19.9 True False False 7m10s kube-storage-version-migrator monitoring network 4.19.9 True True False 6m56s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.19.9 True True False 38s Waiting for 1/3 Profiles to be applied openshift-apiserver 4.19.9 True False False 7m10s openshift-controller-manager 4.19.9 True False False 7m10s openshift-samples operator-lifecycle-manager 4.19.9 True False False 7m15s operator-lifecycle-manager-catalog 4.19.9 True False False 7m11s operator-lifecycle-manager-packageserver 4.19.9 True False False 7m10s service-ca storage 4.19.9 True False False 96s 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 8m23s dns 4.19.9 False True True 8m23s DNS "default" is unavailable. image-registry False True True 7m25s Available: The deployment does not have available replicas... ingress False True True 8m3s 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 30s kube-apiserver 4.19.9 True False False 8m11s kube-controller-manager 4.19.9 True False False 8m11s kube-scheduler 4.19.9 True False False 8m11s kube-storage-version-migrator 4.19.9 True False False 26s monitoring Unknown True Unknown 1s Rolling out the stack. network 4.19.9 True True False 7m57s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes) node-tuning 4.19.9 True False False 99s openshift-apiserver 4.19.9 True False False 8m11s openshift-controller-manager 4.19.9 True False False 8m11s openshift-samples operator-lifecycle-manager 4.19.9 True False False 8m16s operator-lifecycle-manager-catalog 4.19.9 True False False 8m12s operator-lifecycle-manager-packageserver 4.19.9 True False False 8m11s service-ca 4.19.9 True False False 27s storage 4.19.9 True False False 2m37s 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 20s csi-snapshot-controller 4.19.9 True False False 9m23s dns 4.19.9 True True False 58s DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3." image-registry 4.19.9 True False False 46s ingress 4.19.9 True False True 31s 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.19.9 True False False 90s kube-apiserver 4.19.9 True False False 9m11s kube-controller-manager 4.19.9 True False False 9m11s kube-scheduler 4.19.9 True False False 9m11s kube-storage-version-migrator 4.19.9 True False False 86s monitoring Unknown True Unknown 61s Rolling out the stack. network 4.19.9 True True False 8m57s DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes) node-tuning 4.19.9 True False False 2m39s openshift-apiserver 4.19.9 True False False 9m11s openshift-controller-manager 4.19.9 True False False 9m11s openshift-samples 4.19.9 True False False 44s operator-lifecycle-manager 4.19.9 True False False 9m16s operator-lifecycle-manager-catalog 4.19.9 True False False 9m12s operator-lifecycle-manager-packageserver 4.19.9 True False False 9m11s service-ca 4.19.9 True False False 87s storage 4.19.9 True False False 3m37s 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 80s csi-snapshot-controller 4.19.9 True False False 10m dns 4.19.9 True True False 118s DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3." image-registry 4.19.9 True False False 106s ingress 4.19.9 True False False 91s insights 4.19.9 True False False 2m30s 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 2m26s monitoring Unknown True Unknown 2m1s Rolling out the stack. network 4.19.9 True False False 9m57s node-tuning 4.19.9 True False False 3m39s 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 104s 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 2m27s storage 4.19.9 True False False 4m37s 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 2m21s csi-snapshot-controller 4.19.9 True False False 11m dns 4.19.9 True False False 2m59s image-registry 4.19.9 True False False 2m47s ingress 4.19.9 True False False 2m32s insights 4.19.9 True False False 3m31s kube-apiserver 4.19.9 True False False 11m kube-controller-manager 4.19.9 True False False 11m kube-scheduler 4.19.9 True False False 11m kube-storage-version-migrator 4.19.9 True False False 3m27s monitoring Unknown True Unknown 3m2s Rolling out the stack. network 4.19.9 True False False 10m node-tuning 4.19.9 True False False 4m40s openshift-apiserver 4.19.9 True False False 11m openshift-controller-manager 4.19.9 True False False 11m openshift-samples 4.19.9 True False False 2m45s operator-lifecycle-manager 4.19.9 True False False 11m operator-lifecycle-manager-catalog 4.19.9 True False False 11m operator-lifecycle-manager-packageserver 4.19.9 True False False 11m service-ca 4.19.9 True False False 3m28s storage 4.19.9 True False False 5m38s 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 3m21s csi-snapshot-controller 4.19.9 True False False 12m dns 4.19.9 True False False 3m59s image-registry 4.19.9 True False False 3m47s ingress 4.19.9 True False False 3m32s insights 4.19.9 True False False 4m31s kube-apiserver 4.19.9 True False False 12m kube-controller-manager 4.19.9 True False False 12m kube-scheduler 4.19.9 True False False 12m kube-storage-version-migrator 4.19.9 True False False 4m27s monitoring Unknown True Unknown 4m2s Rolling out the stack. network 4.19.9 True False False 11m node-tuning 4.19.9 True False False 5m40s openshift-apiserver 4.19.9 True False False 12m openshift-controller-manager 4.19.9 True False False 12m openshift-samples 4.19.9 True False False 3m45s operator-lifecycle-manager 4.19.9 True False False 12m operator-lifecycle-manager-catalog 4.19.9 True False False 12m operator-lifecycle-manager-packageserver 4.19.9 True False False 12m service-ca 4.19.9 True False False 4m28s storage 4.19.9 True False False 6m38s 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 4m21s csi-snapshot-controller 4.19.9 True False False 13m dns 4.19.9 True False False 4m59s image-registry 4.19.9 True False False 4m47s ingress 4.19.9 True False False 4m32s insights 4.19.9 True False False 5m31s kube-apiserver 4.19.9 True False False 13m kube-controller-manager 4.19.9 True False False 13m kube-scheduler 4.19.9 True False False 13m kube-storage-version-migrator 4.19.9 True False False 5m27s monitoring 4.19.9 True False False 56s network 4.19.9 True False False 12m node-tuning 4.19.9 True False False 6m40s openshift-apiserver 4.19.9 True False False 13m openshift-controller-manager 4.19.9 True False False 13m openshift-samples 4.19.9 True False False 4m45s operator-lifecycle-manager 4.19.9 True False False 13m operator-lifecycle-manager-catalog 4.19.9 True False False 13m operator-lifecycle-manager-packageserver 4.19.9 True False False 13m service-ca 4.19.9 True False False 5m28s storage 4.19.9 True False False 7m38s 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 5m22s csi-snapshot-controller 4.19.9 True False False 14m dns 4.19.9 True False False 6m image-registry 4.19.9 True False False 5m48s ingress 4.19.9 True False False 5m33s insights 4.19.9 True False False 6m32s kube-apiserver 4.19.9 True False False 14m kube-controller-manager 4.19.9 True False False 14m kube-scheduler 4.19.9 True False False 14m kube-storage-version-migrator 4.19.9 True False False 6m28s monitoring 4.19.9 True False False 117s network 4.19.9 True False False 13m node-tuning 4.19.9 True False False 7m41s openshift-apiserver 4.19.9 True False False 14m openshift-controller-manager 4.19.9 True False False 14m openshift-samples 4.19.9 True False False 5m46s operator-lifecycle-manager 4.19.9 True False False 14m operator-lifecycle-manager-catalog 4.19.9 True False False 14m operator-lifecycle-manager-packageserver 4.19.9 True False False 14m service-ca 4.19.9 True False False 6m29s storage 4.19.9 True False False 8m39s Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!