This is a known issue affecting VMware Cloud Foundation 4.x versions.
VMware engineering is aware of this issue and is working to fix it in a future release.
Workaround:
a) Finding the Bundle ID you want to delete from the API:
On your SDDC Manager:
Deleting the Bundle using the script on the SDDC Manager Appliance:
# su
{Enter the password to elevate to root}
# /opt/vmware/vcf/lcm/lcm-app/bin/bundle_cleanup.py {Bundle_id}
Example:
# /opt/vmware/vcf/lcm/lcm-app/bin/bundle_cleanup.py ########-####-####-####-##########69
When the script has run completely, you see below output in the /var/log/vmware/vcf/lcm/bundle_cleanup.log file:
2021-03-08 12:18:31,809 [INFO] root: Performing cleanup for bundle with IDs : ['########-####-####-####-##########69'] 2021-03-08 12:18:31,809 [INFO] root: Execute cmd: psql --host=localhost -U postg res -d lcm -tc "select count(*) from upgrade where upgrade_status in ('INPROGRES S','CANCELLING');" 2021-03-08 12:18:31,848 [INFO] root: b' 0\n' ..... ..... ..... 2021-03-08 12:18:32,990 [INFO] root: Bundle with ID :########-####-####-####-##########69 not found in partner_bundle_metadata table 2021-03-08 12:18:32,991 [INFO] root: Starting LCM service. 2021-03-08 12:18:32,991 [INFO] root: Execute cmd: systemctl start lcm 2021-03-08 12:18:33,135 [INFO] root: RC: 0 2021-03-08 12:18:33,136 [INFO] root: Out:
Note: It will take a few minutes for the Bundle services to restart, and you may see the message “Depot still initializing”.