-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14
-
Important
-
No
-
CLOUD Sprint 244
-
1
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-20369. The following is the description of the original issue:
—
Description of problem:
worker CSR are pending, so no worker nodes available
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-10-06-234925
How reproducible:
Always
Steps to Reproduce:
Create a cluster with profile - aws-c2s-ipi-disconnected-private-fips
Actual results:
Workers csrs are pending
Expected results:
workers should be up and running all CSRs approved
Additional info:
failed to find machine for node ip-10-143-1-120” , in logs of cluster-machine-approver Seems like we should have ips like “ip-10-143-1-120.ec2.internal” failing here - https://github.com/openshift/cluster-machine-approver/blob/master/pkg/controller/csr_check.go#L263
Must-gather - https://drive.google.com/file/d/15tz9TLdTXrH6bSBSfhlIJ1l_nzeFE1R3/view?usp=sharing
template for installation - https://gitlab.cee.redhat.com/aosqe/flexy-templates/-/blob/master/functionality-testing/aos-4_14/ipi-on-aws/versioned-installer-customer_vpc-disconnected_private_cluster-fips-c2s-ci
- clones
-
OCPBUGS-20369 worker CSR are pending, so no worker nodes available
- Closed
- is blocked by
-
OCPBUGS-20369 worker CSR are pending, so no worker nodes available
- Closed
- links to
-
RHBA-2023:6837 OpenShift Container Platform 4.14.z bug fix update