Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. 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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 4.16.0
    • 4.13, 4.12, 4.14, 4.15, 4.16
    • Installer / IBM Cloud
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when deleting a private cluster on IBM Cloud that used the same domain name as a non-private IBM Cloud cluster, some resources were not deleted. With this update, all private cluster resources are deleted when the cluster is destroyed. (link:https://issues.redhat.com/browse/OCPBUGS-28870[*OCPBUGS-28870*])
      Show
      * Previously, when deleting a private cluster on IBM Cloud that used the same domain name as a non-private IBM Cloud cluster, some resources were not deleted. With this update, all private cluster resources are deleted when the cluster is destroyed. (link: https://issues.redhat.com/browse/OCPBUGS-28870 [* OCPBUGS-28870 *])
    • Bug Fix
    • Done

      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. 

            jeffbnowicki Jeff Nowicki
            maxu@redhat.com May Xu
            May Xu May Xu
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: