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

[vsphere] one vm folder is not deleted when destroying ocp cluster configured region/zone

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, when destroying a partially deployed cluster after an installation failed on VMWare vSphere, some virtual machine folders were not destroyed. This error could occur in clusters configured with multiple vSphere datacenters or multiple vSphere clusters. With this update, all installer-provisioned infrastructure is correctly deleted when destroying a partially deployed cluster after an installation failure. (link:https://issues.redhat.com/browse/OCPBUGS-1489[*OCPBUGS-1489*])
      Show
      Previously, when destroying a partially deployed cluster after an installation failed on VMWare vSphere, some virtual machine folders were not destroyed. This error could occur in clusters configured with multiple vSphere datacenters or multiple vSphere clusters. With this update, all installer-provisioned infrastructure is correctly deleted when destroying a partially deployed cluster after an installation failure. (link: https://issues.redhat.com/browse/OCPBUGS-1489 [* OCPBUGS-1489 *])
    • Done

      Description of problem:

      Deploy IPI cluster on multi datacenter/cluster vsphere env, installer failed with some reason, then tried to destroy cluster, and found that one vm folder under one of datacenters is not deleted.
      
      When installer exit, following objects are attached with tag jima15b-cq7z7
      sh-4.4$ govc tags.attached.ls jima15b-cq7z7 | xargs govc ls -L
      /IBMCloud/vm/jima15b-cq7z7
      /datacenter-2/vm/jima15b-cq7z7
      /datacenter-2/vm/jima15b-cq7z7/jima15b-cq7z7-rhcos-us-west-us-west-1a
      /IBMCloud/vm/jima15b-cq7z7/jima15b-cq7z7-rhcos-us-east-us-east-2a
      /IBMCloud/vm/jima15b-cq7z7/jima15b-cq7z7-rhcos-us-east-us-east-3a
      /IBMCloud/vm/jima15b-cq7z7/jima15b-cq7z7-rhcos-us-east-us-east-1a
      /IBMCloud/vm/jima15b-cq7z7/jima15b-cq7z7-bootstrap
      
      sh-4.4$ ./openshift-install destroy cluster --dir ipi_missingzones/
      INFO Destroyed                                     VirtualMachine=jima15b-cq7z7-rhcos-us-west-us-west-1a
      INFO Destroyed                                     VirtualMachine=jima15b-cq7z7-rhcos-us-east-us-east-2a
      INFO Destroyed                                     VirtualMachine=jima15b-cq7z7-rhcos-us-east-us-east-3a
      INFO Destroyed                                     VirtualMachine=jima15b-cq7z7-rhcos-us-east-us-east-1a
      INFO Destroyed                                     VirtualMachine=jima15b-cq7z7-bootstrap
      INFO Destroyed                                     Folder=jima15b-cq7z7
      INFO Deleted                                       Tag=jima15b-cq7z7
      INFO Deleted                                       TagCategory=openshift-jima15b-cq7z7
      INFO Time elapsed: 55s       
      
      After destroying cluster, folder jima15b-cq7z7 is still there, not deleted.
      sh-4.4$ govc ls /datacenter-2/vm/ | grep jima15b-cq7z7
      /datacenter-2/vm/jima15b-cq7z7                    

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

      4.12.0-0.nightly-2022-09-18-141547

      How reproducible:

      always when installer fails to create infrastructure, it works when installation is successful. 

      Steps to Reproduce:

      1. deploy IPI cluster on vsphere env configured multi datacenter/cluster
      2. installer failed to create infrastructure with some reason
      3. destroy cluster
      4. one folder is not deleted 
      

      Actual results:

      one folder is not deleted

      Expected results:

      All infrastructures created by installer should be removed

      Additional info:

       

              jcallen@redhat.com Joseph Callen
              jinyunma Jinyun Ma
              Jinyun Ma Jinyun Ma
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: