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-03T09:51:55Z 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-4acb94b496' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-4acb94b496' 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-4acb94b496 Domain Prefix: kx-4acb94b496 Display Name: kx-4acb94b496 ID: 2l2s3g9u0ssf40g12d7ckp03djvp5l69 External ID: 8e9f47dd-77d5-4b76-98f8-b4513907d784 Control Plane: ROSA Service Hosted OpenShift Version: 4.16.46 Channel Group: stable DNS: Not ready AWS Account: 418295695583 AWS Billing Account: 418295695583 API URL: Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ - Data Plane: MultiAZ Nodes: - Compute (desired): 3 - Compute (current): 0 Network: - Type: OVNKubernetes - Service CIDR: 172.30.0.0/16 - Machine CIDR: 10.0.0.0/16 - Pod CIDR: 10.128.0.0/14 - Host Prefix: /23 - Subnets: subnet-001fc23497e4a3aeb, subnet-00ffba09365a434bc, subnet-074cbf0329958194a, subnet-0689cd077699b690a, subnet-0f9f09e46f74cde64, subnet-033f48892ddbaa09d EC2 Metadata Http Tokens: optional Role (STS) ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role Support Role ARN: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role Instance IAM Roles: - Worker: arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role Operator IAM Roles: - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Sep 3 2025 09:52:04 UTC User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/32BTmTMoW38Bf3CxfeWKJr1eYtO 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-4acb94b496'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-4acb94b496 --watch'. INFO: Track the progress of the cluster creation... W: Region flag will be removed from this command in future versions INFO: Cluster 'kx-4acb94b496' 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-4acb94b496 Version 2025-09-03 09:56:02 +0000 UTC hostedclusters kx-4acb94b496 ValidAWSIdentityProvider StatusUnknown 2025-09-03 09:56:03 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-09-03 09:56:03 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Ignition server deployment not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 HostedCluster is supported by operator configuration 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Release image is valid 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Reconciliation active on resource 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:06 +0000 UTC hostedclusters kx-4acb94b496 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-03 09:56:06 +0000 UTC hostedclusters kx-4acb94b496 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-4acb94b496 Version 2025-09-03 09:56:02 +0000 UTC hostedclusters kx-4acb94b496 ValidAWSIdentityProvider StatusUnknown 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Ignition server deployment not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Condition not found in the CVO. 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Reconciliation active on resource 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 HostedCluster is supported by operator configuration 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 Release image is valid 2025-09-03 09:56:05 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is not found 2025-09-03 09:56:06 +0000 UTC hostedclusters kx-4acb94b496 configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-09-03 09:56:06 +0000 UTC hostedclusters kx-4acb94b496 HostedCluster is at expected version 2025-09-03 09:57:34 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-09-03 09:57:36 +0000 UTC hostedclusters kx-4acb94b496 Configuration passes validation 2025-09-03 09:57:38 +0000 UTC hostedclusters kx-4acb94b496 Required platform credentials are found 2025-09-03 09:57:40 +0000 UTC hostedclusters kx-4acb94b496 Configuration passes validation 2025-09-03 09:57:40 +0000 UTC hostedclusters kx-4acb94b496 lookup api.kx-4acb94b496.kkod.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-09-03 09:57:40 +0000 UTC hostedclusters kx-4acb94b496 EtcdAvailable StatefulSetNotFound 2025-09-03 09:57:40 +0000 UTC hostedclusters kx-4acb94b496 AWS KMS is not configured 2025-09-03 09:57:40 +0000 UTC hostedclusters kx-4acb94b496 Kube APIServer deployment not found 2025-09-03 09:57:40 +0000 UTC hostedclusters kx-4acb94b496 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-0be1a5bbaceb5664c'\n\tstatus code: 400, request id: 0eb7bf6a-00bd-4cd2-899f-20e1a7e2bef1"; private-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-0be1a5bbaceb5664c'\n\tstatus code: 400, request id: d6771e3f-b446-4598-80a2-163d4ee51d44"; 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-0be1a5bbaceb5664c'\n\tstatus code: 400, request id: 0eb7bf6a-00bd-4cd2-899f-20e1a7e2bef1" 2025-09-03 09:57:44 +0000 UTC hostedclusters kx-4acb94b496 capi-provider deployment has 2 unavailable replicas 2025-09-03 09:57:47 +0000 UTC hostedclusters kx-4acb94b496 OIDC configuration is valid 2025-09-03 09:57:47 +0000 UTC hostedclusters kx-4acb94b496 Reconciliation completed successfully 2025-09-03 09:58:09 +0000 UTC hostedclusters kx-4acb94b496 WebIdentityErr 2025-09-03 09:59:10 +0000 UTC hostedclusters kx-4acb94b496 All is well 2025-09-03 09:59:21 +0000 UTC hostedclusters kx-4acb94b496 All is well 2025-09-03 09:59:57 +0000 UTC hostedclusters kx-4acb94b496 EtcdAvailable QuorumAvailable 2025-09-03 10:00:23 +0000 UTC hostedclusters kx-4acb94b496 Kube APIServer deployment is available 2025-09-03 10:00:38 +0000 UTC hostedclusters kx-4acb94b496 The hosted cluster is not degraded 2025-09-03 10:00:40 +0000 UTC hostedclusters kx-4acb94b496 All is well 2025-09-03 10:00:43 +0000 UTC hostedclusters kx-4acb94b496 [kube-controller-manager deployment has 1 unavailable replicas, router deployment has 1 unavailable replicas] 2025-09-03 10:00:51 +0000 UTC hostedclusters kx-4acb94b496 All is well 2025-09-03 10:00:54 +0000 UTC hostedclusters kx-4acb94b496 The hosted control plane is available INFO: Cluster 'kx-4acb94b496' 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.46 True False False 2m36s dns 4.16.46 False False True 2m37s DNS "default" is unavailable. image-registry False True True 112s Available: The deployment does not have available replicas... ingress False True True 2m20s 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.46 True False False 2m25s kube-controller-manager 4.16.46 True False False 2m25s kube-scheduler 4.16.46 True False False 2m25s kube-storage-version-migrator monitoring network 4.16.46 True True False 2m13s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 2m26s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.46 True False False 2m25s openshift-controller-manager 4.16.46 True False False 2m25s openshift-samples operator-lifecycle-manager 4.16.46 True False False 2m27s operator-lifecycle-manager-catalog 4.16.46 True False False 2m27s operator-lifecycle-manager-packageserver 4.16.46 True False False 2m25s service-ca storage 4.16.46 False False False 2m25s 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.46 True False False 2m36s dns 4.16.46 False False True 2m37s DNS "default" is unavailable. image-registry False True True 112s Available: The deployment does not have available replicas... ingress False True True 2m20s 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.46 True False False 2m25s kube-controller-manager 4.16.46 True False False 2m25s kube-scheduler 4.16.46 True False False 2m25s kube-storage-version-migrator monitoring network 4.16.46 True True False 2m13s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 2m26s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.46 True False False 2m25s openshift-controller-manager 4.16.46 True False False 2m25s openshift-samples operator-lifecycle-manager 4.16.46 True False False 2m27s operator-lifecycle-manager-catalog 4.16.46 True False False 2m27s operator-lifecycle-manager-packageserver 4.16.46 True False False 2m25s service-ca storage 4.16.46 False False False 2m25s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s Unable to connect to the server: dial tcp: lookup api.kx-4acb94b496.kkod.p3.openshiftapps.com on 172.30.0.10:53: no such host 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.46 True False False 4m37s dns 4.16.46 False False True 4m38s DNS "default" is unavailable. image-registry False True True 3m53s Available: The deployment does not have available replicas... ingress False True True 4m21s 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.46 True False False 4m26s kube-controller-manager 4.16.46 True False False 4m26s kube-scheduler 4.16.46 True False False 4m26s kube-storage-version-migrator monitoring network 4.16.46 True True False 4m14s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 4m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.46 True False False 4m26s openshift-controller-manager 4.16.46 True False False 4m26s openshift-samples operator-lifecycle-manager 4.16.46 True False False 4m28s operator-lifecycle-manager-catalog 4.16.46 True False False 4m28s operator-lifecycle-manager-packageserver 4.16.46 True False False 4m26s service-ca storage 4.16.46 False False False 4m26s 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.46 True False False 5m37s dns 4.16.46 False False True 5m38s DNS "default" is unavailable. image-registry False True True 4m53s Available: The deployment does not have available replicas... ingress False True True 5m21s 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.46 True False False 5m26s kube-controller-manager 4.16.46 True False False 5m26s kube-scheduler 4.16.46 True False False 5m26s kube-storage-version-migrator monitoring network 4.16.46 True True False 5m14s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 5m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.46 True False False 5m26s openshift-controller-manager 4.16.46 True False False 5m26s openshift-samples operator-lifecycle-manager 4.16.46 True False False 5m28s operator-lifecycle-manager-catalog 4.16.46 True False False 5m28s operator-lifecycle-manager-packageserver 4.16.46 True False False 5m26s service-ca storage 4.16.46 False False False 5m26s 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.46 True False False 6m37s dns 4.16.46 False False True 6m38s DNS "default" is unavailable. image-registry False True True 5m53s Available: The deployment does not have available replicas... ingress False True True 6m21s 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.46 True False False 6m26s kube-controller-manager 4.16.46 True False False 6m26s kube-scheduler 4.16.46 True False False 6m26s kube-storage-version-migrator monitoring network 4.16.46 True True False 6m14s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning False True False 6m27s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.16.46 True False False 6m26s openshift-controller-manager 4.16.46 True False False 6m26s openshift-samples operator-lifecycle-manager 4.16.46 True False False 6m28s operator-lifecycle-manager-catalog 4.16.46 True False False 6m28s operator-lifecycle-manager-packageserver 4.16.46 True False False 6m26s service-ca storage 4.16.46 False False False 6m26s 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.46 True False False 7m38s dns 4.16.46 False False True 7m39s DNS "default" is unavailable. image-registry False True True 6m54s Available: The deployment does not have available replicas... ingress False True True 7m22s 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.46 True False False 7m27s kube-controller-manager 4.16.46 True False False 7m27s kube-scheduler 4.16.46 True False False 7m27s kube-storage-version-migrator monitoring network 4.16.46 True True False 7m15s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.16.46 True True False 2s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.16.46 True False False 7m27s openshift-controller-manager 4.16.46 True False False 7m27s openshift-samples operator-lifecycle-manager 4.16.46 True False False 7m29s operator-lifecycle-manager-catalog 4.16.46 True False False 7m29s operator-lifecycle-manager-packageserver 4.16.46 True False False 7m27s service-ca storage 4.16.46 False True False 7m27s 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.46 True False False 8m38s dns 4.16.46 False True True 8m39s DNS "default" is unavailable. image-registry False True True 7m54s Available: The deployment does not have available replicas... ingress False True True 8m22s 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.46 True False False 8m27s kube-controller-manager 4.16.46 True False False 8m27s kube-scheduler 4.16.46 True False False 8m27s kube-storage-version-migrator monitoring network 4.16.46 True True False 8m15s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready node-tuning 4.16.46 True False False 62s openshift-apiserver 4.16.46 True False False 8m27s openshift-controller-manager 4.16.46 True False False 8m27s openshift-samples operator-lifecycle-manager 4.16.46 True False False 8m29s operator-lifecycle-manager-catalog 4.16.46 True False False 8m29s operator-lifecycle-manager-packageserver 4.16.46 True False False 8m27s service-ca storage 4.16.46 True False False 59s 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.46 True False False 9m38s dns 4.16.46 False True True 9m39s DNS "default" is unavailable. image-registry False True True 8m54s Available: The deployment does not have available replicas... ingress False True True 9m22s 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.46 True False False 9m27s kube-controller-manager 4.16.46 True False False 9m27s kube-scheduler 4.16.46 True False False 9m27s kube-storage-version-migrator monitoring network 4.16.46 True True False 9m15s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.16.46 True True False 44s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.46 True False False 9m27s openshift-controller-manager 4.16.46 True False False 9m27s openshift-samples operator-lifecycle-manager 4.16.46 True False False 9m29s operator-lifecycle-manager-catalog 4.16.46 True False False 9m29s operator-lifecycle-manager-packageserver 4.16.46 True False False 9m27s service-ca storage 4.16.46 True False False 119s 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.46 True False False 10m dns 4.16.46 False True True 10m DNS "default" is unavailable. image-registry False True True 9m54s Available: The deployment does not have available replicas... ingress False True True 10m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.16.46 True False False 10m kube-controller-manager 4.16.46 True False False 10m kube-scheduler 4.16.46 True False False 10m kube-storage-version-migrator monitoring network 4.16.46 True True False 10m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.16.46 True True False 104s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.46 True False False 10m openshift-controller-manager 4.16.46 True False False 10m openshift-samples operator-lifecycle-manager 4.16.46 True False False 10m operator-lifecycle-manager-catalog 4.16.46 True False False 10m operator-lifecycle-manager-packageserver 4.16.46 True False False 10m service-ca storage 4.16.46 True False False 2m59s 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.46 True False False 11m dns 4.16.46 False True True 11m DNS "default" is unavailable. image-registry False True True 10m Available: The deployment does not have available replicas... ingress False True True 11m 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.46 True False False 11m kube-controller-manager 4.16.46 True False False 11m kube-scheduler 4.16.46 True False False 11m kube-storage-version-migrator monitoring network 4.16.46 True True False 11m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.16.46 True True False 2m45s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.46 True False False 11m openshift-controller-manager 4.16.46 True False False 11m openshift-samples operator-lifecycle-manager 4.16.46 True False False 11m operator-lifecycle-manager-catalog 4.16.46 True False False 11m operator-lifecycle-manager-packageserver 4.16.46 True False False 11m service-ca storage 4.16.46 True False False 4m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 False True False 4s DeploymentAvailable: 0 replicas available for console deployment csi-snapshot-controller 4.16.46 True False False 12m dns 4.16.46 True False False 20s image-registry True True False 16s Progressing: The deployment has not completed... ingress False True True 12m 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.46 True False False 60s kube-apiserver 4.16.46 True False False 12m kube-controller-manager 4.16.46 True False False 12m kube-scheduler 4.16.46 True False False 12m kube-storage-version-migrator 4.16.46 True False False 58s monitoring Unknown True Unknown 29s Rolling out the stack. network 4.16.46 True True False 12m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.16.46 True True False 3m45s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.46 True False False 12m openshift-controller-manager 4.16.46 True False False 12m openshift-samples 4.16.46 True False False 14s operator-lifecycle-manager 4.16.46 True False False 12m operator-lifecycle-manager-catalog 4.16.46 True False False 12m operator-lifecycle-manager-packageserver 4.16.46 True False False 12m service-ca 4.16.46 True False False 58s storage 4.16.46 True False False 5m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True True False 51s SyncLoopRefreshProgressing: working toward version 4.16.46, 1 replicas available csi-snapshot-controller 4.16.46 True False False 13m dns 4.16.46 True False False 80s image-registry True True True 76s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-85cbb54676" has timed out progressing. ingress 4.16.46 False True True 24s 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.46 True False False 2m kube-apiserver 4.16.46 True False False 13m kube-controller-manager 4.16.46 True False False 13m kube-scheduler 4.16.46 True False False 13m kube-storage-version-migrator 4.16.46 True False False 118s monitoring Unknown True Unknown 89s Rolling out the stack. network 4.16.46 True True True 13m DaemonSet "/openshift-multus/multus" rollout is not making progress - pod multus-hd8tm is in CrashLoopBackOff State node-tuning 4.16.46 True True False 4m45s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.46 True False False 13m openshift-controller-manager 4.16.46 True False False 13m openshift-samples 4.16.46 True False False 74s operator-lifecycle-manager 4.16.46 True False False 13m operator-lifecycle-manager-catalog 4.16.46 True False False 13m operator-lifecycle-manager-packageserver 4.16.46 True False False 13m service-ca 4.16.46 True False False 118s storage 4.16.46 True False False 6m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True True False 111s SyncLoopRefreshProgressing: working toward version 4.16.46, 1 replicas available csi-snapshot-controller 4.16.46 True False False 14m dns 4.16.46 True False False 2m20s image-registry True True True 2m16s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-85cbb54676" has timed out progressing. ingress 4.16.46 True True False 6s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination...... insights 4.16.46 True False False 3m kube-apiserver 4.16.46 True False False 14m kube-controller-manager 4.16.46 True False False 14m kube-scheduler 4.16.46 True False False 14m kube-storage-version-migrator 4.16.46 True False False 2m58s monitoring Unknown True Unknown 2m29s Rolling out the stack. network 4.16.46 True True True 14m DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" rollout is not making progress - pod ovnkube-node-q4mnj is in CrashLoopBackOff State node-tuning 4.16.46 True True False 5m45s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.16.46 True False False 14m openshift-controller-manager 4.16.46 True False False 14m openshift-samples 4.16.46 True False False 2m14s operator-lifecycle-manager 4.16.46 True False False 14m operator-lifecycle-manager-catalog 4.16.46 True False False 14m operator-lifecycle-manager-packageserver 4.16.46 True False False 14m service-ca 4.16.46 True False False 2m58s storage 4.16.46 True False False 7m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True True False 2m52s SyncLoopRefreshProgressing: working toward version 4.16.46, 1 replicas available csi-snapshot-controller 4.16.46 True False False 15m dns 4.16.46 True False False 3m21s image-registry True True True 3m17s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-85cbb54676" has timed out progressing. ingress 4.16.46 False True False 25s 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.46 True False False 4m1s kube-apiserver 4.16.46 True False False 15m kube-controller-manager 4.16.46 True False False 15m kube-scheduler 4.16.46 True False False 15m kube-storage-version-migrator 4.16.46 True False False 3m59s monitoring Unknown True Unknown 3m30s Rolling out the stack. network 4.16.46 True True True 15m DaemonSet "/openshift-multus/multus" rollout is not making progress - pod multus-hd8tm is in CrashLoopBackOff State node-tuning 4.16.46 True False False 6m46s openshift-apiserver 4.16.46 True False False 15m openshift-controller-manager 4.16.46 True False False 15m openshift-samples 4.16.46 True False False 3m15s operator-lifecycle-manager 4.16.46 True False False 15m operator-lifecycle-manager-catalog 4.16.46 True False False 15m operator-lifecycle-manager-packageserver 4.16.46 True False False 15m service-ca 4.16.46 True False False 3m59s storage 4.16.46 True False False 8m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True True False 3m52s SyncLoopRefreshProgressing: working toward version 4.16.46, 1 replicas available csi-snapshot-controller 4.16.46 True False False 16m dns 4.16.46 True False False 4m21s image-registry True True True 4m17s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-85cbb54676" has timed out progressing. ingress 4.16.46 True True False 6s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.16.46 True False False 5m1s kube-apiserver 4.16.46 True False False 16m kube-controller-manager 4.16.46 True False False 16m kube-scheduler 4.16.46 True False False 16m kube-storage-version-migrator 4.16.46 True False False 4m59s monitoring Unknown True Unknown 4m30s Rolling out the stack. network 4.16.46 True True False 16m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.16.46 True False False 7m46s openshift-apiserver 4.16.46 True False False 16m openshift-controller-manager 4.16.46 True False False 16m openshift-samples 4.16.46 True False False 4m15s operator-lifecycle-manager 4.16.46 True False False 16m operator-lifecycle-manager-catalog 4.16.46 True False False 16m operator-lifecycle-manager-packageserver 4.16.46 True False False 16m service-ca 4.16.46 True False False 4m59s storage 4.16.46 True False False 9m1s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True False False 4m52s csi-snapshot-controller 4.16.46 True False False 17m dns 4.16.46 True False False 5m21s image-registry 4.16.46 True False False 5m17s ingress 4.16.46 True False False 66s insights 4.16.46 True False False 6m1s kube-apiserver 4.16.46 True False False 17m kube-controller-manager 4.16.46 True False False 17m kube-scheduler 4.16.46 True False False 17m kube-storage-version-migrator 4.16.46 True False False 5m59s monitoring Unknown True Unknown 5m30s Rolling out the stack. network 4.16.46 True False False 17m node-tuning 4.16.46 True False False 8m46s openshift-apiserver 4.16.46 True False False 17m openshift-controller-manager 4.16.46 True False False 17m openshift-samples 4.16.46 True False False 5m15s operator-lifecycle-manager 4.16.46 True False False 17m operator-lifecycle-manager-catalog 4.16.46 True False False 17m operator-lifecycle-manager-packageserver 4.16.46 True False False 17m service-ca 4.16.46 True False False 5m59s storage 4.16.46 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.46 True False False 5m53s csi-snapshot-controller 4.16.46 True False False 18m dns 4.16.46 True True False 6m22s DNS "default" reports Progressing=True: "Have 2 available node-resolver pods, want 3." image-registry 4.16.46 True True False 6m18s Progressing: The registry is ready... ingress 4.16.46 True False False 2m7s insights 4.16.46 True False False 7m2s kube-apiserver 4.16.46 True False False 18m kube-controller-manager 4.16.46 True False False 18m kube-scheduler 4.16.46 True False False 18m kube-storage-version-migrator 4.16.46 True False False 7m monitoring Unknown True Unknown 6m31s Rolling out the stack. network 4.16.46 True True False 18m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.16.46 True True False 16s Waiting for 1/3 Profiles to be applied openshift-apiserver 4.16.46 True False False 18m openshift-controller-manager 4.16.46 True False False 18m openshift-samples 4.16.46 True False False 6m16s operator-lifecycle-manager 4.16.46 True False False 18m operator-lifecycle-manager-catalog 4.16.46 True False False 18m operator-lifecycle-manager-packageserver 4.16.46 True False False 18m service-ca 4.16.46 True False False 7m storage 4.16.46 True True False 11m 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.46 True False False 6m53s csi-snapshot-controller 4.16.46 True False False 19m dns 4.16.46 True False False 7m22s image-registry 4.16.46 True False False 7m18s ingress 4.16.46 True False False 3m7s insights 4.16.46 True False False 8m2s kube-apiserver 4.16.46 True False False 19m kube-controller-manager 4.16.46 True False False 19m kube-scheduler 4.16.46 True False False 19m kube-storage-version-migrator 4.16.46 True False False 8m monitoring Unknown True Unknown 7m31s Rolling out the stack. network 4.16.46 True False False 19m node-tuning 4.16.46 True False False 76s openshift-apiserver 4.16.46 True False False 19m openshift-controller-manager 4.16.46 True False False 19m openshift-samples 4.16.46 True False False 7m16s operator-lifecycle-manager 4.16.46 True False False 19m operator-lifecycle-manager-catalog 4.16.46 True False False 19m operator-lifecycle-manager-packageserver 4.16.46 True False False 19m service-ca 4.16.46 True False False 8m storage 4.16.46 True False False 12m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True False False 7m53s csi-snapshot-controller 4.16.46 True False False 20m dns 4.16.46 True False False 8m22s image-registry 4.16.46 True False False 8m18s ingress 4.16.46 True False False 4m7s insights 4.16.46 True False False 9m2s kube-apiserver 4.16.46 True False False 20m kube-controller-manager 4.16.46 True False False 20m kube-scheduler 4.16.46 True False False 20m kube-storage-version-migrator 4.16.46 True False False 9m monitoring 4.16.46 True False False 23s network 4.16.46 True False False 20m node-tuning 4.16.46 True False False 2m16s openshift-apiserver 4.16.46 True False False 20m openshift-controller-manager 4.16.46 True False False 20m openshift-samples 4.16.46 True False False 8m16s operator-lifecycle-manager 4.16.46 True False False 20m operator-lifecycle-manager-catalog 4.16.46 True False False 20m operator-lifecycle-manager-packageserver 4.16.46 True False False 20m service-ca 4.16.46 True False False 9m storage 4.16.46 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.46 True False False 8m53s csi-snapshot-controller 4.16.46 True False False 21m dns 4.16.46 True False False 9m22s image-registry 4.16.46 True False False 9m18s ingress 4.16.46 True False False 5m7s insights 4.16.46 True False False 10m kube-apiserver 4.16.46 True False False 21m kube-controller-manager 4.16.46 True False False 21m kube-scheduler 4.16.46 True False False 21m kube-storage-version-migrator 4.16.46 True False False 10m monitoring 4.16.46 True False False 83s network 4.16.46 True False False 21m node-tuning 4.16.46 True False False 3m16s openshift-apiserver 4.16.46 True False False 21m openshift-controller-manager 4.16.46 True False False 21m openshift-samples 4.16.46 True False False 9m16s operator-lifecycle-manager 4.16.46 True False False 21m operator-lifecycle-manager-catalog 4.16.46 True False False 21m operator-lifecycle-manager-packageserver 4.16.46 True False False 21m service-ca 4.16.46 True False False 10m storage 4.16.46 True False False 14m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True False False 9m54s csi-snapshot-controller 4.16.46 True False False 22m dns 4.16.46 True False False 10m image-registry 4.16.46 True False False 10m ingress 4.16.46 True False False 6m8s insights 4.16.46 True False False 11m kube-apiserver 4.16.46 True False False 22m kube-controller-manager 4.16.46 True False False 22m kube-scheduler 4.16.46 True False False 22m kube-storage-version-migrator 4.16.46 True False False 11m monitoring 4.16.46 True False False 2m24s network 4.16.46 True False False 22m node-tuning 4.16.46 True False False 4m17s openshift-apiserver 4.16.46 True False False 22m openshift-controller-manager 4.16.46 True False False 22m openshift-samples 4.16.46 True False False 10m operator-lifecycle-manager 4.16.46 True False False 22m operator-lifecycle-manager-catalog 4.16.46 True False False 22m operator-lifecycle-manager-packageserver 4.16.46 True False False 22m service-ca 4.16.46 True False False 11m storage 4.16.46 True False False 15m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.16.46 True False False 10m csi-snapshot-controller 4.16.46 True False False 23m dns 4.16.46 True False False 11m image-registry 4.16.46 True False False 11m ingress 4.16.46 True False False 7m8s insights 4.16.46 True False False 12m kube-apiserver 4.16.46 True False False 23m kube-controller-manager 4.16.46 True False False 23m kube-scheduler 4.16.46 True False False 23m kube-storage-version-migrator 4.16.46 True False False 12m monitoring 4.16.46 True False False 3m24s network 4.16.46 True False False 23m node-tuning 4.16.46 True False False 5m17s openshift-apiserver 4.16.46 True False False 23m openshift-controller-manager 4.16.46 True False False 23m openshift-samples 4.16.46 True False False 11m operator-lifecycle-manager 4.16.46 True False False 23m operator-lifecycle-manager-catalog 4.16.46 True False False 23m operator-lifecycle-manager-packageserver 4.16.46 True False False 23m service-ca 4.16.46 True False False 12m storage 4.16.46 True False False 16m Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!