-
Bug
-
Resolution: Unresolved
-
Major
-
4.19.0
Description of problem:
While testing on https://github.com/openshift/machine-config-operator/pull/4800#issuecomment-2628801965, we found the worker can't fetch Ignition successfully so it couldn't be started well. The worker machine console serial log shows: �[K[�[0m�[0;31m* �[0m] A start job is running for Ignition (fetch) (50min 30s / no limit) [ 3034.007742] ignition[823]: GET https://api-int.gpei-0201-gcpdns.qe.gcp.devcluster.openshift.com:22623/config/worker: attempt #607 [ 3034.044185] ignition[823]: GET error: Get "https://api-int.gpei-0201-gcpdns.qe.gcp.devcluster.openshift.com:22623/config/worker": dial tcp: lookup api-int.gpei-0201-gcpdns.qe.gcp.devcluster.openshift.com on 169.254.169.254:53: no such host
Version-Release number of selected component (if applicable):
Payload built based on https://github.com/openshift/machine-config-operator/pull/4800, https://prow.ci.openshift.org/view/gs/test-platform-results/logs/release-openshift-origin-installer-launch-aws-modern/1885498038630223872
How reproducible:
Always
Steps to Reproduce:
1. Create a 4.19 cluster with customDNS feature enabled: featureSet: CustomNoUpgrade featureGates: - GCPClusterHostedDNS=true
Actual results:
Expected results:
Additional info:
- blocks
-
HIVE-1812 Support external DNS for OpenShift on GCP
-
- Dev Complete
-
-
OCPBUGS-49915 [Custom DNS] Workers can't fetch ignition from master nodes
-
- POST
-
-
OCPSTRAT-990 [GA] Allow customer managed DNS solutions for GCP: Implementation
-
- In Progress
-
- is cloned by
-
OCPBUGS-49915 [Custom DNS] Workers can't fetch ignition from master nodes
-
- POST
-
- links to