Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-12371

vSphere deprovisioning fails on 4.16 when folder is used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • MCE 2.6.0
    • Cluster Lifecycle
    • None
    • True
    • Fix required is in OCP - OCPBUGS-36351
    • False
    • Release Notes
    • Hide
      Deprovisioning vSphere clusters of OpenShift 4.16 with versions lower than 4.16.3 can fail when a pre-existing vSphere folder was used for provisioning. In order to work around and complete the deprovisioning, please detach the tag from the pre-existing folder prior to destroying the cluster.
      Show
      Deprovisioning vSphere clusters of OpenShift 4.16 with versions lower than 4.16.3 can fail when a pre-existing vSphere folder was used for provisioning. In order to work around and complete the deprovisioning, please detach the tag from the pre-existing folder prior to destroying the cluster.
    • Known Issue
    • Proposed
    • Critical
    • Yes

      Description of problem:

      When deprovisioning vSphere clusterdeployment, the destroy/uninstall pod gets stuck at the end when it checks the folder is emptied, even though the folder is being used by other cluster deployments:

      time="2024-06-25T14:21:23Z" level=debug msg="Power Off Virtual Machines"
time="2024-06-25T14:21:25Z" level=debug msg="Delete Virtual Machines"
time="2024-06-25T14:21:27Z" level=debug msg="Delete Folder"
time="2024-06-25T14:21:30Z" level=error msg="Folder should be empty but contains 90 objects: VirtualMachine:vm-205925, VirtualMachine:vm-205921, VirtualMachine:vm-205924, VirtualMachine:vm-189243, VirtualMachine:vm-205585, VirtualMachine:vm-205934, VirtualMachine:vm-198466, VirtualMachine:vm-205609, VirtualMachine:vm-205580, VirtualMachine:vm-93243, VirtualMachine:vm-205835, VirtualMachine:vm-205892, VirtualMachine:vm-205916, VirtualMachine:vm-205932, VirtualMachine:vm-206008, VirtualMachine:vm-205893, VirtualMachine:vm-205922, VirtualMachine:vm-206007, VirtualMachine:vm-205923, VirtualMachine:vm-205622, VirtualMachine:vm-205754, VirtualMachine:vm-205837, VirtualMachine:vm-205593, VirtualMachine:vm-205706, VirtualMachine:vm-205579, VirtualMachine:vm-205849, VirtualMachine:vm-205928, VirtualMachine:vm-205919, VirtualMachine:vm-206006, VirtualMachine:vm-205685, VirtualMachine:vm-205584, VirtualMachine:vm-205836, VirtualMachine:vm-205577, VirtualMachine:vm-206001, VirtualMachine:vm-13348, VirtualMachine:vm-206003, VirtualMachine:vm-200694, VirtualMachine:vm-205918, VirtualMachine:vm-205850, VirtualMachine:vm-205891, VirtualMachine:vm-205830, VirtualMachine:vm-206004, VirtualMachine:vm-205917, VirtualMachine:vm-205914, VirtualMachine:vm-205631, VirtualMachine:vm-205854, VirtualMachine:vm-205833, VirtualMachine:vm-13110, VirtualMachine:vm-207005, VirtualMachine:vm-205930, VirtualMachine:vm-189083, VirtualMachine:vm-205887, VirtualMachine:vm-205913, VirtualMachine:vm-205655, VirtualMachine:vm-205582, VirtualMachine:vm-205915, VirtualMachine:vm-193089, VirtualMachine:vm-89009, VirtualMachine:vm-205617, VirtualMachine:vm-87043, VirtualMachine:vm-205911, VirtualMachine:vm-205853, VirtualMachine:vm-205894, VirtualMachine:vm-205929, VirtualMachine:vm-205889, VirtualMachine:vm-205852, VirtualMachine:vm-206002, VirtualMachine:vm-198425, VirtualMachine:vm-205664, VirtualMachine:vm-189235, VirtualMachine:vm-205890, VirtualMachine:vm-205926, VirtualMachine:vm-207003, VirtualMachine:vm-205601, VirtualMachine:vm-205927, VirtualMachine:vm-100001, VirtualMachine:vm-205583, VirtualMachine:vm-205847, VirtualMachine:vm-205933, VirtualMachine:vm-205832, VirtualMachine:vm-174430, VirtualMachine:vm-205581, VirtualMachine:vm-200299, VirtualMachine:vm-207001, VirtualMachine:vm-207008, VirtualMachine:vm-207006, VirtualMachine:vm-205851, VirtualMachine:vm-207004, VirtualMachine:vm-207007, VirtualMachine:vm-205834. The installer will retry removing \"virtualmachine\" objects, but any other type will need to be removed manually before the deprovision can proceed" Folder=ACM-QE
time="2024-06-25T14:21:30Z" level=debug msg="Folder: Expected Folder ACM-QE to be empty"

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

      MCE 2.6.0-DOWNANDBACK-2024-06-25-01-09-57

      How reproducible:

      Steps to Reproduce:

      1. deploy vsphere with folder
      2. deploy another vpshere into same folder
      3. deprovision vsphere cluster in from step 1

      Actual results:

      Expected results:

      Additional info:

              xiangli@redhat.com Xiangjing Li
              rhn-support-dhuynh David Huynh
              David Huynh David Huynh
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: