Deleting an Organization vDC results in an Internal Server Error

Products

• VMware Cloud Director

Issue/Introduction

• When there is an attempt to decommission an Organization, the deletion process fails during the removal of the Datacenter Group within the VMware Cloud Director (vCD) UI.
• This deletion attempt triggers an Internal Server Error with the following specific database constraint violation: 

  [ <UUID> ] Internal Server Error - could not delete: [com.vmware.vcloud.common.model.logicalresource.StorageClassVdcLogicalResourceModel#<UUID>] - ERROR: update or delete on table "vdc_logical_resource" violates foreign key constraint "fk_libr_stor_pro2vdc_logi_reso" on table "library_storage_profiles" Detail: Key (id)=(<UUID>) is still referenced from table "library_storage_profiles".

Environment

VMware Cloud Director 10.6.x

Cause

• This failure is attributed to stale entries and orphaned records within the vCD database that the automated UI cleanup process failed to reconcile.
• The database maintains a strict Relational Integrity model. The record in the vdc_logical_resource table acts as a "parent" to a record in the library_storage_profiles table. Because a Foreign Key (FK) constraint (fk_libr_stor_pro2vdc_logi_reso) exists between these two tables, the system prevents the deletion of the logical resource to avoid leaving orphaned "child" records. Since the standard UI workflow did not clear these library profiles first, the entire decommissioning thread is blocked.

Resolution

Required to manually resolve the dependency chain by purging the stale records in the correct relational order (child records followed by parent records) in order to delete the Organization. For required database modifications, please open a Support Request with Broadcom Technical Support and cite this Article ID (436169) in the problem description. For more information, see Creating and managing Broadcom support cases.