Unable to clean up stale vCenter and Organization VDC in VMware Cloud Director
search cancel

Unable to clean up stale vCenter and Organization VDC in VMware Cloud Director

book

Article ID: 371253

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • One of the vCenter connected to VMware Cloud Director (VCD) was decommissioned and in VCD we can still see all the objects for the not existing vCenter (Org VDC, vApp, VMs, PVDC).
  • The decommissioned vCenter is shown as disconnected state in VCD UI.
  • When deleting the Org VDC connected to the not existing vCenter (including VM and vApp) the task fails with below error and only the VMs in the Org VDC are deleted:
    The operation failed because vCenter Server "VCENTER-NAME" is not connected
  • Using the below force delete API on those objects fails since vCenter is in a disconnected state:
    DELETE https://vcloud.example.com/api/vApp/{vAppUrn}?force=true
    DELETE https://vcloud.example.com/api/virtualCenters/{vcUrn}?force=true
  • The vApp deletion will still fail with the error
    The operation failed because vCenter Server is not Connected

 

 

 

Environment

VMware Cloud Director 10.4 

Cause

When vCenter is in disconnected state, not all the objects connected to the disconnected vCenter can be deleted from the UI.

Resolution

The stale entries for the vApp, Network connected to the disconnected vCenter need to be manually deleted from VCD Database

Please open a case with Broadcom Support to delete the stale entries from VCD Database. For more information, see Creating and managing Broadcom support cases