This is a clone of issue OCPBUGS-28870. The following is the description of the original issue:
—
Description of problem:
Install a private cluster, the base domain set in install-config.yaml is same as another existed cis domain name. After destroy the private cluster, the dns resource-records remains.
Version-Release number of selected component (if applicable):
4.15
How reproducible:
Always
Steps to Reproduce:
1.create a DNS service instance, setting its domain to "ibmcloud.qe.devcluster.openshift.com", Note, this domain name is also being used in another existing CIS domain. 2.Install a private ibmcloud cluster, the base domain set in install-config is "ibmcloud.qe.devcluster.openshift.com" 3.Destroy the cluster 4.Check the remains dns records
Actual results:
$ ibmcloud dns resource-records 5f8a0c4d-46c2-4daa-9157-97cb9ad9033a -i preserved-openshift-qe-private | grep ci-op-17qygd06-23ac4 api-int.ci-op-17qygd06-23ac4.ibmcloud.qe.devcluster.openshift.com *.apps.ci-op-17qygd06-23ac4.ibmcloud.qe.devcluster.openshift.com api.ci-op-17qygd06-23ac4.ibmcloud.qe.devcluster.openshift.com
Expected results:
No more dns records about the cluster
Additional info:
$ ibmcloud dns zones -i preserved-openshift-qe-private | awk '{print $2}'
Name
private-ibmcloud.qe.devcluster.openshift.com
private-ibmcloud-1.qe.devcluster.openshift.com
ibmcloud.qe.devcluster.openshift.com
$ ibmcloud cis domains
Name
ibmcloud.qe.devcluster.openshift.com
When use private-ibmcloud.qe.devcluster.openshift.com and private-ibmcloud-1.qe.devcluster.openshift.com as domain, no such issue, when use ibmcloud.qe.devcluster.openshift.com as domain the dns records remains.
- clones
-
OCPBUGS-28870 [IBMCloud] dns records from a private cluster are not destroyed when it is using the same domain name as another existing CIS instance
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to
-
RHBA-2024:1559
OpenShift Container Platform 4.15.z bug fix update
