Bug 1733389 - When multiple DNS zones with the same name exist, the wrong zone ID can be used
Summary: When multiple DNS zones with the same name exist, the wrong zone ID can be used
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.4.z
Assignee: John Hixson
QA Contact: Yang Yang
: 1729123 (view as bug list)
Depends On: 1805540
TreeView+ depends on / blocked
Reported: 2019-07-25 23:01 UTC by John Hixson
Modified: 2020-03-03 18:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-03-03 18:25:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description John Hixson 2019-07-25 23:01:10 UTC
Description of problem:

It is possible in both AWS and Azure (probably GCP as well), to create DNS zones with the same name for different regions and resource groups. When multiple zones with the same name exist, they are mapped onto a single zone in the installer. This in turn, will pick the first zone ID out of the group. This is not necessarily correct all of the time, nor desired. 

How reproducible: 

Can be reproduced 100% of the time. 

Steps to Reproduce:
1. Login to https://console.aws.amazon.com
2. Go to Route 53 -> Hosted zones
3. Create hosted zone with domain "installer.devcluster.openshift.com"
4. Repeat step 3 four more times
5. Logout
6. Run the installer: openshift-install create manifests --dir .
7. For platform, pecify aws
8. For base domain, specify installer.devcluster.openshift.com
9. Pick a name and use your pull secret and let the installer run
10. Once the installer exits, look at the manifests/cluster-dns-02-config.yml file
11. Look at the id field under publicZone
12. This ID will always be the ID of the first created DNS Zone
13. Verify this ID with the ID's of the other zones created on AWS

Actual results:

    id: Z3URY6TWQ91KVV

Expected results:

    id: <ID of a different same name zone>

Comment 3 Abhinav Dahiya 2020-02-07 23:12:03 UTC
*** Bug 1729123 has been marked as a duplicate of this bug. ***

Comment 4 John Hixson 2020-02-11 03:21:24 UTC
Updated PR: https://github.com/openshift/installer/pull/2764

Comment 5 Scott Dodson 2020-03-03 18:25:48 UTC
This requires a new field in the installer and is therefore not valid for backporting to 4.4.

Note You need to log in before you can comment on or make changes to this bug.