-
Bug
-
Resolution: Unresolved
-
Critical
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
Rejected
-
Installer Sprint 271, Installer Sprint 272, Installer Sprint 273, Installer Sprint 274, Installer Sprint 275, Installer Sprint 277, Installer Sprint 278
-
7
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Create a custom DNS cluster, bootbuke.log shows:
Jun 11 07:49:18 ip-10-0-97-96 bootkube.sh[4730]: Created "configmap-admin-kubeconfig-client-ca.yaml" configmaps.v1./admin-kubeconfig-client-ca -n openshift-config
Jun 11 08:07:21 ip-10-0-97-96 cluster-bootstrap[4776]: Error: error while checking pod status: timed out waiting for the condition
Jun 11 08:07:21 ip-10-0-97-96 cluster-bootstrap[4776]: Tearing down temporary bootstrap control plane...
Jun 11 08:07:21 ip-10-0-97-96 bootkube.sh[4730]: Error: error while checking pod status: timed out waiting for the condition
Jun 11 08:07:21 ip-10-0-97-96 bootkube.sh[4730]: Tearing down temporary bootstrap control plane...
Jun 11 08:07:21 ip-10-0-97-96 bootkube.sh[4730]: Error: error while checking pod status: timed out waiting for the condition
Jun 11 08:07:21 ip-10-0-97-96 cluster-bootstrap[4776]: Error: error while checking pod status: timed out waiting for the condition
Version-Release number of selected component (if applicable):
4.20.0-0.nightly-2025-06-09-022311
How reproducible:
Always
Steps to Reproduce:
1.Create a custom dns cluster with config:
platform:
aws:
userProvisionedDNS: Enabled
featureSet: CustomNoUpgrade
featureGates:
- AWSClusterHostedDNS=true
2.
3.
Actual results:
As described
Expected results:
Bootstrap process could complete successfully.
Additional info:
- blocks
-
OCPSTRAT-992 [Dev Preview]: Allow customer managed DNS solutions for AWS: Implementation
-
- In Progress
-
- links to