Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-44507

Azure destroy idempotence: BaseDomainResourceGroup

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.6.z
    • Installer / openshift-installer
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When destroying an azure cluster, if the main resource group has already been destroyed, DNS entries are not scrubbed, despite BaseDomainResourceGroup being provided via metadata.

      Version-Release number of selected component (if applicable):

      Probably many. I think I have been reproducing in 4.16 and/or 4.17.

      How reproducible:

      Easy, 100%

      Steps to Reproduce:

          1. Install azure cluster with distinct BaseDomainResourceGroup . Save metadata.json. Confirm it contains BaseDomainResourceGroup.
    2. Manually (via cloud API/CLI) destroy main resource group.
    3. Destroy cluster, providing metadata.json from step 1.

      Actual results:

      DNS records still exist.

      Expected results:

      DNS records scrubbed.

      Additional info:
      thread

              rna-afk Aditya Narayanaswamy
              efried.openshift Eric Fried
              Gaoyun Pei Gaoyun Pei
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: