Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1815071

Summary: GCP install with an config of an running cluster leads previous running cluster does not work
Product: OpenShift Container Platform Reporter: Yang Yang <yanyang>
Component: InstallerAssignee: Abhinav Dahiya <adahiya>
Installer sub component: openshift-installer QA Contact: Yang Yang <yanyang>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: low    
Version: 4.5   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 18:06:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
installation log for cluster#1
none
installation log for cluster#2 none

Description Yang Yang 2020-03-19 12:12:52 UTC 
Description of problem:
There exists an up and running GCP cluster#1. Then create GCP cluster#2 with the same install config with cluster#1. The cluster#2 installs successfully. Yet the 1st cluster does not work any more. An installation should not have side effect on an running cluster.

Version-Release number of the following components:
4.5.0-0.nightly-2020-03-18-092618

How reproducible:
Always

Steps to Reproduce:
1. Create GCP cluster#1 with install-config.yaml
2. Check above cluster works well
3. Create GCP cluster#2 with install-config.yaml

Actual results:
Cluser#2 installs successfully but cluster#1 does not work any more

Expected results:
Block the installation of cluster#2 and cluster#1 works as before

Additional info:
Prior to 4.5, cluster#2 install will be terminated since dns record already exists which is expected.

With 4.4, following error out:
11:20:26 level=error msg="Error: Error creating DNS RecordSet: googleapi: Error 409: The resource 'entity.change.additions[0]' named 'api.yy.cn.qe.gcp.devcluster.openshift.com. (A)' already exists, alreadyExists"
Comment 1 Abhinav Dahiya 2020-05-11 17:18:20 UTC 
can you include the log files from installer .openshift_install.log for the runs you mentioned?
Comment 2 Yang Yang 2020-05-12 03:45:18 UTC 
Created attachment 1687518 [details]
installation log for cluster#1
Comment 3 Yang Yang 2020-05-12 03:45:46 UTC 
Created attachment 1687519 [details]
installation log for cluster#2
Comment 6 Yang Yang 2020-05-15 03:23:06 UTC 
Verify it with 4.5.0-0.nightly-2020-05-15-011814

Steps to verify:
1. Install a GCP cluster#1 with install-config.yaml
2. Check cluster#1 works well
3. Install a GCP cluster#2 with install-config.yaml

The installation of cluster#2 fails with below error and cluster#1 still works.

level=fatal msg="failed to fetch Cluster: failed to fetch dependency of \"Cluster\": failed to generate asset \"Platform Provisioning Check\": metadata.name: Invalid value: \"yanyang\": record api.yanyang.qe.gcp.devcluster.openshift.com. already exists in DNS Zone (openshift-qe/qe) and might be in use by another cluster, please remove it to continue"

The test results are as expected, hence move it to verified state
Comment 8 errata-xmlrpc 2020-08-04 18:06:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5 image release advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409