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 'konflux-ci-418295695583' 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-b91d8f42ea' INFO: To view a list of clusters and their status, run 'rosa list clusters' INFO: Cluster 'kx-b91d8f42ea' 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-b91d8f42ea Domain Prefix: kx-b91d8f42ea Display Name: kx-b91d8f42ea ID: 2m93jolrqcl9hsgq2u2iaj6f8a1fst3h External ID: 402fbb1f-e246-456a-a74e-3d9cb7a05aec Control Plane: ROSA Service Hosted OpenShift Version: 4.17.42 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-kube-system-kube-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent Managed Policies: Yes State: waiting (Waiting for user action) Private: No Delete Protection: Disabled Created: Oct 31 2025 09:56:54 UTC [DEPRECATED] User Workload Monitoring: Enabled Details Page: https://console.redhat.com/openshift/details/s/34pJWjqdlf3AEX8ndJkEryRIFi8 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-b91d8f42ea'. INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-b91d8f42ea --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-b91d8f42ea' 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-b91d8f42ea Version 2025-10-31 10:00:42 +0000 UTC hostedclusters kx-b91d8f42ea ValidAWSIdentityProvider StatusUnknown 2025-10-31 10:00:43 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-31 10:00:43 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea ValidConfiguration condition is false: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Ignition server deployment not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is supported by operator configuration 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Release image is valid 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation active on resource 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is not found 2025-10-31 10:00:47 +0000 UTC hostedclusters kx-b91d8f42ea configuration is invalid: NamedCertificates get secret: Invalid value: "cluster-api-cert": Secret "cluster-api-cert" not found 2025-10-31 10:00:47 +0000 UTC hostedclusters kx-b91d8f42ea 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-b91d8f42ea Version 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Release image is valid 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Waiting for hosted control plane kubeconfig to be created 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is supported by operator configuration 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Ignition server deployment not found 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation active on resource 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:47 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is at expected version 2025-10-31 10:02:12 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-31 10:02:19 +0000 UTC hostedclusters kx-b91d8f42ea Configuration passes validation 2025-10-31 10:02:21 +0000 UTC hostedclusters kx-b91d8f42ea Required platform credentials are found 2025-10-31 10:02:23 +0000 UTC hostedclusters kx-b91d8f42ea OIDC configuration is valid 2025-10-31 10:02:23 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation completed successfully 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea AWS KMS is not configured 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea capi-provider deployment has 1 unavailable replicas 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea lookup api.kx-b91d8f42ea.81r1.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea Configuration passes validation 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea Waiting for etcd to reach quorum 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea Kube APIServer deployment not found 2025-10-31 10:02:33 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:02:47 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:02:52 +0000 UTC hostedclusters kx-b91d8f42ea WebIdentityErr 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-b91d8f42ea Version 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Release image is valid 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation active on resource 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Get "https://ad158ded5fd4645768945a49afd987d2-b50c3428f142dcdc.elb.us-east-1.amazonaws.com:443/healthz": dial tcp: lookup ad158ded5fd4645768945a49afd987d2-b50c3428f142dcdc.elb.us-east-1.amazonaws.com on 172.30.0.10:53: no such host 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is supported by operator configuration 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:00:47 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is at expected version 2025-10-31 10:02:12 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-31 10:02:19 +0000 UTC hostedclusters kx-b91d8f42ea Configuration passes validation 2025-10-31 10:02:21 +0000 UTC hostedclusters kx-b91d8f42ea Required platform credentials are found 2025-10-31 10:02:23 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation completed successfully 2025-10-31 10:02:23 +0000 UTC hostedclusters kx-b91d8f42ea OIDC configuration is valid 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea AWS KMS is not configured 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea [capi-provider deployment has 2 unavailable replicas, catalog-operator deployment has 1 unavailable replicas, certified-operators-catalog deployment has 2 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, cluster-storage-operator deployment has 1 unavailable replicas, community-operators-catalog deployment has 2 unavailable replicas, dns-operator deployment has 1 unavailable replicas, hosted-cluster-config-operator deployment has 1 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, olm-operator deployment has 1 unavailable replicas, packageserver deployment has 3 unavailable replicas, redhat-marketplace-catalog deployment has 2 unavailable replicas, redhat-operators-catalog deployment has 2 unavailable replicas, router deployment has 2 unavailable replicas] 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea lookup api.kx-b91d8f42ea.81r1.p3.openshiftapps.com on 172.30.0.10:53: no such host 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea Configuration passes validation 2025-10-31 10:02:33 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:02:47 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:03:05 +0000 UTC hostedclusters kx-b91d8f42ea EtcdAvailable QuorumAvailable 2025-10-31 10:03:31 +0000 UTC hostedclusters kx-b91d8f42ea Kube APIServer deployment is available 2025-10-31 10:03:52 +0000 UTC hostedclusters kx-b91d8f42ea Ignition server deployment is available 2025-10-31 10:03:53 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:03:58 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea ClusterVersionAvailable FromClusterVersion 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea Unable to apply 4.17.42: an unknown error has occurred: MultipleErrors 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea Payload loaded version="4.17.42" image="quay.io/openshift-release-dev/ocp-release@sha256:9b7b9909a1f064d5238f35f6e5fc9ac275a0d463a74e8c545544755d953a46d9" architecture="Multi" 2025-10-31 10:04:41 +0000 UTC hostedclusters kx-b91d8f42ea Multiple errors are preventing progress: * Cluster operators console, dns, ingress, insights, kube-storage-version-migrator, monitoring, network, node-tuning, openshift-samples, service-ca are not available * Could not update imagestream "openshift/driver-toolkit" (438 of 621): resource may have been deleted * Could not update operatorgroup "openshift-monitoring/openshift-cluster-monitoring" (550 of 621): resource may have been deleted * Could not update role "openshift-authentication/prometheus-k8s" (537 of 621): resource may have been deleted * Could not update role "openshift-console-operator/prometheus-k8s" (579 of 621): resource may have been deleted * Could not update role "openshift-console/prometheus-k8s" (583 of 621): resource may have been deleted * Could not update role "openshift-ingress-operator/prometheus-k8s" (590 of 621): resource may have been deleted * Could not update role "openshift-kube-apiserver-operator/prometheus-k8s" (594 of 621): resource may have been deleted 2025-10-31 10:04:51 +0000 UTC hostedclusters kx-b91d8f42ea All is well 0001-01-01 00:00:00 +0000 UTC hostedclusters kx-b91d8f42ea Version 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation active on resource 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea Release image is valid 2025-10-31 10:00:46 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is supported by operator configuration 2025-10-31 10:00:47 +0000 UTC hostedclusters kx-b91d8f42ea HostedCluster is at expected version 2025-10-31 10:02:12 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired 2025-10-31 10:02:19 +0000 UTC hostedclusters kx-b91d8f42ea Configuration passes validation 2025-10-31 10:02:21 +0000 UTC hostedclusters kx-b91d8f42ea Required platform credentials are found 2025-10-31 10:02:23 +0000 UTC hostedclusters kx-b91d8f42ea Reconciliation completed successfully 2025-10-31 10:02:23 +0000 UTC hostedclusters kx-b91d8f42ea OIDC configuration is valid 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea Configuration passes validation 2025-10-31 10:02:24 +0000 UTC hostedclusters kx-b91d8f42ea AWS KMS is not configured 2025-10-31 10:02:33 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:02:47 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:03:05 +0000 UTC hostedclusters kx-b91d8f42ea EtcdAvailable QuorumAvailable 2025-10-31 10:03:31 +0000 UTC hostedclusters kx-b91d8f42ea Kube APIServer deployment is available 2025-10-31 10:03:52 +0000 UTC hostedclusters kx-b91d8f42ea Ignition server deployment is available 2025-10-31 10:03:53 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:03:58 +0000 UTC hostedclusters kx-b91d8f42ea All is well 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea Unable to apply 4.17.42: some cluster operators are not available 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea Condition not found in the CVO. 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea Payload loaded version="4.17.42" image="quay.io/openshift-release-dev/ocp-release@sha256:9b7b9909a1f064d5238f35f6e5fc9ac275a0d463a74e8c545544755d953a46d9" architecture="Multi" 2025-10-31 10:04:05 +0000 UTC hostedclusters kx-b91d8f42ea ClusterVersionAvailable FromClusterVersion 2025-10-31 10:04:41 +0000 UTC hostedclusters kx-b91d8f42ea Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available 2025-10-31 10:05:10 +0000 UTC hostedclusters kx-b91d8f42ea The hosted cluster is not degraded 2025-10-31 10:05:19 +0000 UTC hostedclusters kx-b91d8f42ea The hosted control plane is available INFO: Cluster 'kx-b91d8f42ea' 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.17.42 True False False 4m21s dns 4.17.42 False False True 4m22s DNS "default" is unavailable. image-registry False True True 4m4s Available: The deployment does not have available replicas... ingress False True True 4m5s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 4m11s kube-controller-manager 4.17.42 True False False 4m11s kube-scheduler 4.17.42 True False False 4m11s kube-storage-version-migrator monitoring network 4.17.42 True True False 3m59s DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m36s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 4m11s openshift-controller-manager 4.17.42 True False False 4m11s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m13s operator-lifecycle-manager-catalog 4.17.42 True False False 4m12s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m11s service-ca storage 4.17.42 False False False 4m11s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service cluster operators to be accessible finished! [INFO] Cluster operators are accessible. Waiting for cluster to be reported as healthy for 60m... NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 4m22s dns 4.17.42 False False True 4m23s DNS "default" is unavailable. image-registry False True True 4m5s Available: The deployment does not have available replicas... ingress False True True 4m6s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 4m12s kube-controller-manager 4.17.42 True False False 4m12s kube-scheduler 4.17.42 True False False 4m12s kube-storage-version-migrator monitoring network 4.17.42 True True False 4m DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 3m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 4m12s openshift-controller-manager 4.17.42 True False False 4m12s openshift-samples operator-lifecycle-manager 4.17.42 True False False 4m14s operator-lifecycle-manager-catalog 4.17.42 True False False 4m13s operator-lifecycle-manager-packageserver 4.17.42 True False False 4m12s service-ca storage 4.17.42 False False False 4m12s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 5m22s dns 4.17.42 False False True 5m23s DNS "default" is unavailable. image-registry False True True 5m5s Available: The deployment does not have available replicas... ingress False True True 5m6s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 5m12s kube-controller-manager 4.17.42 True False False 5m12s kube-scheduler 4.17.42 True False False 5m12s kube-storage-version-migrator monitoring network 4.17.42 True True False 5m DaemonSet "/openshift-network-operator/iptables-alerter" is waiting for other operators to become ready... node-tuning False True False 4m37s DaemonSet "tuned" has no available Pod(s) openshift-apiserver 4.17.42 True False False 5m12s openshift-controller-manager 4.17.42 True False False 5m12s openshift-samples operator-lifecycle-manager 4.17.42 True False False 5m14s operator-lifecycle-manager-catalog 4.17.42 True False False 5m13s operator-lifecycle-manager-packageserver 4.17.42 True False False 5m12s service-ca storage 4.17.42 False False False 5m12s AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 6m22s dns 4.17.42 False False True 6m23s DNS "default" is unavailable. image-registry False True True 6m5s Available: The deployment does not have available replicas... ingress False True True 6m6s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 6m12s kube-controller-manager 4.17.42 True False False 6m12s kube-scheduler 4.17.42 True False False 6m12s kube-storage-version-migrator monitoring network 4.17.42 True True False 6m DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.17.42 True True False 22s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.17.42 True False False 6m12s openshift-controller-manager 4.17.42 True False False 6m12s openshift-samples operator-lifecycle-manager 4.17.42 True False False 6m14s operator-lifecycle-manager-catalog 4.17.42 True False False 6m13s operator-lifecycle-manager-packageserver 4.17.42 True False False 6m12s service-ca storage 4.17.42 True False False 12s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 7m22s dns 4.17.42 False False True 7m23s DNS "default" is unavailable. image-registry False True True 7m5s Available: The deployment does not have available replicas... ingress False True True 7m6s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 7m12s kube-controller-manager 4.17.42 True False False 7m12s kube-scheduler 4.17.42 True False False 7m12s kube-storage-version-migrator monitoring network 4.17.42 True True False 7m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True True False 82s Waiting for 1/1 Profiles to be applied openshift-apiserver 4.17.42 True False False 7m12s openshift-controller-manager 4.17.42 True False False 7m12s openshift-samples operator-lifecycle-manager 4.17.42 True False False 7m14s operator-lifecycle-manager-catalog 4.17.42 True False False 7m13s operator-lifecycle-manager-packageserver 4.17.42 True False False 7m12s service-ca storage 4.17.42 True False False 72s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 8m23s dns 4.17.42 False False True 8m24s DNS "default" is unavailable. image-registry False True True 8m6s Available: The deployment does not have available replicas... ingress False True True 8m7s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 8m13s kube-controller-manager 4.17.42 True False False 8m13s kube-scheduler 4.17.42 True False False 8m13s kube-storage-version-migrator monitoring network 4.17.42 True True False 8m1s DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True True False 41s Waiting for 2/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 8m13s openshift-controller-manager 4.17.42 True False False 8m13s openshift-samples operator-lifecycle-manager 4.17.42 True False False 8m15s operator-lifecycle-manager-catalog 4.17.42 True False False 8m14s operator-lifecycle-manager-packageserver 4.17.42 True False False 8m13s service-ca storage 4.17.42 True False False 2m13s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 9m23s dns 4.17.42 False False True 9m24s DNS "default" is unavailable. image-registry False True True 9m6s Available: The deployment does not have available replicas... ingress False True True 9m7s The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights kube-apiserver 4.17.42 True False False 9m13s kube-controller-manager 4.17.42 True False False 9m13s kube-scheduler 4.17.42 True False False 9m13s kube-storage-version-migrator monitoring network 4.17.42 True True False 9m1s DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 101s Waiting for 2/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 9m13s openshift-controller-manager 4.17.42 True False False 9m13s openshift-samples operator-lifecycle-manager 4.17.42 True False False 9m15s operator-lifecycle-manager-catalog 4.17.42 True False False 9m14s operator-lifecycle-manager-packageserver 4.17.42 True False False 9m13s service-ca storage 4.17.42 True False False 3m13s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 10m dns 4.17.42 False False True 10m DNS "default" is unavailable. image-registry False True True 10m 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.17.42 True False False 10m kube-controller-manager 4.17.42 True False False 10m kube-scheduler 4.17.42 True False False 10m kube-storage-version-migrator monitoring network 4.17.42 True True False 10m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True True False 2m41s Waiting for 2/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 10m openshift-controller-manager 4.17.42 True False False 10m openshift-samples operator-lifecycle-manager 4.17.42 True False False 10m operator-lifecycle-manager-catalog 4.17.42 True False False 10m operator-lifecycle-manager-packageserver 4.17.42 True False False 10m service-ca storage 4.17.42 True False False 4m13s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 11m dns 4.17.42 False False True 11m DNS "default" is unavailable. image-registry False True True 11m 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.17.42 True False False 11m kube-controller-manager 4.17.42 True False False 11m kube-scheduler 4.17.42 True False False 11m kube-storage-version-migrator monitoring network 4.17.42 True True False 11m DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" is not available (awaiting 2 nodes)... node-tuning 4.17.42 True True False 3m41s Waiting for 2/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 11m openshift-controller-manager 4.17.42 True False False 11m openshift-samples operator-lifecycle-manager 4.17.42 True False False 11m operator-lifecycle-manager-catalog 4.17.42 True False False 11m operator-lifecycle-manager-packageserver 4.17.42 True False False 11m service-ca storage 4.17.42 True False False 5m13s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 12m dns 4.17.42 False False True 12m DNS "default" is unavailable. image-registry False True True 12m Available: The deployment does not have available replicas... 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 kube-apiserver 4.17.42 True False False 12m kube-controller-manager 4.17.42 True False False 12m kube-scheduler 4.17.42 True False False 12m kube-storage-version-migrator monitoring network 4.17.42 True True True 12m DaemonSet "/openshift-multus/multus" rollout is not making progress - pod multus-lm489 is in CrashLoopBackOff State node-tuning 4.17.42 True True False 4m41s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 12m openshift-controller-manager 4.17.42 True False False 12m openshift-samples operator-lifecycle-manager 4.17.42 True False False 12m operator-lifecycle-manager-catalog 4.17.42 True False False 12m operator-lifecycle-manager-packageserver 4.17.42 True False False 12m service-ca storage 4.17.42 True False False 6m13s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console csi-snapshot-controller 4.17.42 True False False 13m dns 4.17.42 False True True 13m DNS "default" is unavailable. image-registry False True True 13m Available: The deployment does not have available replicas... ingress False True True 13m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.) insights 4.17.42 True False False 9s kube-apiserver 4.17.42 True False False 13m kube-controller-manager 4.17.42 True False False 13m kube-scheduler 4.17.42 True False False 13m kube-storage-version-migrator 4.17.42 True False False 5s monitoring network 4.17.42 True True False 13m DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready... node-tuning 4.17.42 True True False 5m42s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 13m openshift-controller-manager 4.17.42 True False False 13m openshift-samples operator-lifecycle-manager 4.17.42 True False False 13m operator-lifecycle-manager-catalog 4.17.42 True False False 13m operator-lifecycle-manager-packageserver 4.17.42 True False False 13m service-ca 4.17.42 True False False 6s storage 4.17.42 True False False 7m14s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 14m dns 4.17.42 True False False 35s image-registry False True True 14m Available: The deployment does not have available replicas... ingress 4.17.42 True True True 11s The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller) insights 4.17.42 True False False 69s kube-apiserver 4.17.42 True False False 14m kube-controller-manager 4.17.42 True False False 14m kube-scheduler 4.17.42 True False False 14m kube-storage-version-migrator 4.17.42 True False False 65s monitoring Unknown True Unknown 41s Rolling out the stack. network 4.17.42 True True True 14m DaemonSet "/openshift-multus/multus" rollout is not making progress - pod multus-tq6lj is in CrashLoopBackOff State node-tuning 4.17.42 True True False 6m42s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 14m openshift-controller-manager 4.17.42 True False False 14m openshift-samples 4.17.42 True False False 23s operator-lifecycle-manager 4.17.42 True False False 14m operator-lifecycle-manager-catalog 4.17.42 True False False 14m operator-lifecycle-manager-packageserver 4.17.42 True False False 14m service-ca 4.17.42 True False False 66s storage 4.17.42 True False False 8m14s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 85s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 15m dns 4.17.42 True False False 95s image-registry True True False 57s Progressing: The deployment has not completed... ingress 4.17.42 True True True 71s 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.17.42 True False False 2m9s kube-apiserver 4.17.42 True False False 15m kube-controller-manager 4.17.42 True False False 15m kube-scheduler 4.17.42 True False False 15m kube-storage-version-migrator 4.17.42 True False False 2m5s monitoring Unknown True Unknown 101s Rolling out the stack. network 4.17.42 True True False 15m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.17.42 True True False 7m42s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 15m openshift-controller-manager 4.17.42 True False False 15m openshift-samples 4.17.42 True False False 83s operator-lifecycle-manager 4.17.42 True False False 15m operator-lifecycle-manager-catalog 4.17.42 True False False 15m operator-lifecycle-manager-packageserver 4.17.42 True False False 15m service-ca 4.17.42 True False False 2m6s storage 4.17.42 True False False 9m14s Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 2m25s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 16m dns 4.17.42 True False False 2m35s image-registry True True True 117s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-6f5866ff89" has timed out progressing. ingress 4.17.42 True True False 2m11s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 3m9s kube-apiserver 4.17.42 True False False 16m kube-controller-manager 4.17.42 True False False 16m kube-scheduler 4.17.42 True False False 16m kube-storage-version-migrator 4.17.42 True False False 3m5s monitoring Unknown True Unknown 2m41s Rolling out the stack. network 4.17.42 True True False 16m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.17.42 True True False 8m42s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 16m openshift-controller-manager 4.17.42 True False False 16m openshift-samples 4.17.42 True False False 2m23s operator-lifecycle-manager 4.17.42 True False False 16m operator-lifecycle-manager-catalog 4.17.42 True False False 16m operator-lifecycle-manager-packageserver 4.17.42 True False False 16m service-ca 4.17.42 True False False 3m6s storage 4.17.42 True False False 10m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 3m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 17m dns 4.17.42 True False False 3m36s image-registry True True True 2m58s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-6f5866ff89" has timed out progressing. ingress 4.17.42 True True False 3m12s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 4m10s kube-apiserver 4.17.42 True False False 17m kube-controller-manager 4.17.42 True False False 17m kube-scheduler 4.17.42 True False False 17m kube-storage-version-migrator 4.17.42 True False False 4m6s monitoring Unknown True Unknown 3m42s Rolling out the stack. network 4.17.42 True True False 17m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes) node-tuning 4.17.42 True True False 9m43s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 17m openshift-controller-manager 4.17.42 True False False 17m openshift-samples 4.17.42 True False False 3m24s operator-lifecycle-manager 4.17.42 True False False 17m operator-lifecycle-manager-catalog 4.17.42 True False False 17m operator-lifecycle-manager-packageserver 4.17.42 True False False 17m service-ca 4.17.42 True False False 4m7s storage 4.17.42 True False False 11m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 4m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 18m dns 4.17.42 True False False 4m36s image-registry True True True 3m58s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-6f5866ff89" has timed out progressing. ingress 4.17.42 True True False 4m12s ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...... insights 4.17.42 True False False 5m10s kube-apiserver 4.17.42 True False False 18m kube-controller-manager 4.17.42 True False False 18m kube-scheduler 4.17.42 True False False 18m kube-storage-version-migrator 4.17.42 True False False 5m6s monitoring Unknown True Unknown 4m42s Rolling out the stack. network 4.17.42 True True False 18m DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)... node-tuning 4.17.42 True True False 30s Waiting for 1/2 Profiles to be applied openshift-apiserver 4.17.42 True False False 18m openshift-controller-manager 4.17.42 True False False 18m openshift-samples 4.17.42 True False False 4m24s operator-lifecycle-manager 4.17.42 True False False 18m operator-lifecycle-manager-catalog 4.17.42 True False False 18m operator-lifecycle-manager-packageserver 4.17.42 True False False 18m service-ca 4.17.42 True False False 5m7s storage 4.17.42 True False False 12m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True False False 5m26s csi-snapshot-controller 4.17.42 True False False 19m dns 4.17.42 True False False 5m36s image-registry 4.17.42 True True False 4m58s Progressing: The deployment has not completed... ingress 4.17.42 True False False 5m12s insights 4.17.42 True False False 6m10s kube-apiserver 4.17.42 True False False 19m kube-controller-manager 4.17.42 True False False 19m kube-scheduler 4.17.42 True False False 19m kube-storage-version-migrator 4.17.42 True False False 6m6s monitoring Unknown True Unknown 5m42s Rolling out the stack. network 4.17.42 True False False 19m node-tuning 4.17.42 True False False 90s openshift-apiserver 4.17.42 True False False 19m openshift-controller-manager 4.17.42 True False False 19m openshift-samples 4.17.42 True False False 5m24s operator-lifecycle-manager 4.17.42 True False False 19m operator-lifecycle-manager-catalog 4.17.42 True False False 19m operator-lifecycle-manager-packageserver 4.17.42 True False False 19m service-ca 4.17.42 True False False 6m7s storage 4.17.42 True False False 13m Waiting for cluster to be reported as healthy... Trying again in 60s NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.42 True True False 6m26s SyncLoopRefreshProgressing: working toward version 4.17.42, 1 replicas available csi-snapshot-controller 4.17.42 True False False 20m dns 4.17.42 True True False 6m36s DNS "default" reports Progressing=True: "Have 2 available node-resolver pods, want 3." image-registry 4.17.42 True True False 5m58s Progressing: The registry is ready... ingress 4.17.42 True False False 6m12s insights 4.17.42 True False False 7m10s kube-apiserver 4.17.42 True False False 20m kube-controller-manager 4.17.42 True False False 20m kube-scheduler 4.17.42 True False False 20m kube-storage-version-migrator 4.17.42 True False False 7m6s monitoring Unknown True Unknown 6m42s Rolling out the stack. network 4.17.42 True True False 20m DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)... node-tuning 4.17.42 True True False 12s Waiting for 1/3 Profiles to be applied openshift-apiserver 4.17.42 True False False 20m openshift-controller-manager 4.17.42 True False False 20m openshift-samples 4.17.42 True False False 6m24s operator-lifecycle-manager 4.17.42 True False False 20m operator-lifecycle-manager-catalog 4.17.42 True False False 20m operator-lifecycle-manager-packageserver 4.17.42 True False False 20m service-ca 4.17.42 True False False 7m7s storage 4.17.42 True True False 14m AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Waiting for cluster to be reported as healthy... Trying again in 60s healthy cluster to be reported as healthy finished!