-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.17.0
-
None
Description of problem:
An IBM Cloud DNS zone does not go into "Active" state unless a permitted network is added to it and so if we try to use a DNS Zone which does not have a VPC attached as a permitted network, the installer fails with the error "failed to get DNS Zone id" when such a zone is attempted to be used. We already have code to attach a permitted network to a DNS Zone, but it cannot be used unless the DNS Zone is in "Active" state. The zone does not even show up in the install-config survey
Version-Release number of selected component (if applicable):
4.16, 4.17
How reproducible:
In the scenario where the user attempts to create a private cluster without attaching a permitted network to the DNS Zone.
Steps to Reproduce:
1. Create an IBM Cloud DNS zone in a DNS instance. 2. openshift-install create install-config [OPTIONS] 3. User created DNS zone won't show up in the selection for DNS Zone 4. Proceed anyway choosing another private DNS zone. 5. Edit the generated install-config and change basedomain to your zone. 6. openshift-install create manifests [OPTIONS] 7. The above step will fail with "failed to get DNS Zone id".
Actual results:
DNS Zone is not visible in the survey and creating manifests fails.
Expected results:
The DNS zone without permitted networks shows up in the survey and the installation completes.
- is related to
-
OCPBUGS-35933 Power VS: VPC network is not permitted for private DNS
- POST
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update