If you’ve been working with VCF Operations 9.1, you may have noticed that on the Build > Lifecycle > VCF Management > Components page, manually-added components such as VCF Operations for Networks, Log Management, Real-Time Metrics or VCF Automation no longer have a “Delete” option available in the UI.

In VCF Operations 9.0, this was possible on the Fleet Management > Lifecycle > Components page by clicking the three vertical dots next to a component and selecting Delete. That option is gone in 9.1.

Broadcom has published KB article 441333 with an attached Python script (cleanup_component.py) for specific failed or stale component scenarios. This is a destructive cleanup tool, not a general-purpose replacement for the product’s supported backup, restore, upgrade or uninstall workflows.

Prerequisites

Before running the cleanup script, make sure the following are in place:

  • Python installed on the system where you will run the script (can be any system with network access to the Fleet and VCF Management Services components).
  • Network access to the Fleet LCM appliance and VCF Services Runtime.
  • Credentials: use admin@local for the VCF Services Runtime username. Enter the password of vmware-system-user; according to KB 441333, that account and admin@local have the same password.
  • FQDN values: replace all placeholder FQDNs such as <fleet-lcm-fqdn> with the actual values. These can be obtained from VCF Operations UI -> Build -> Lifecycle -> VCF Management -> Components (e.g., vsp01.example.com for <vcf-services-runtime-fqdn>).

Warning: Before cleanup, verify that usable backups exist for every piece of critical component data that must be retained, including logs and databases. Do not treat this workflow, or a VM snapshot taken outside a product-supported procedure, as a way to restore a deleted component.

Supported Scope and Safety Restrictions

Use the script only for a scenario explicitly covered by the current version of KB 441333, such as a duplicate 9.0 component import, an incorrect FQDN that requires a full redeployment or a component that must be removed before a fresh deployment.

For VCF Automation 9.1, the restrictions are especially important:

  • The workflow completely removes VCF Automation from the Fleet.
  • Use it only for permanent removal or to prepare for a fresh deployment.
  • A fresh deployment performed after this cleanup must not be restored from the removed deployment’s backup as part of this workflow. Use Broadcom’s separate Redeploy and Restore VCF Automation procedure when restoration is required.
  • Do not use this procedure to clean up a VCF Automation upgrade failure. Contact Broadcom Support for that scenario.
  • Do not use it to clean up and then import an existing VCF Automation 9.1 system.

For imported 9.0 components, read the component-specific note before deleting anything: some operations remove only the Fleet lifecycle record and leave the existing 9.0 deployment intact. A failed upgrade entry can also remain visible after cleanup; KB 441333 states that this entry does not block subsequent upgrade tasks.

Download and Verify the Script

Download cleanup_component.py from KB 441333 (attached at the bottom of the article).

Verify the SHA256 checksum before running:

sha256sum cleanup_component.py

Expected checksum for the script currently attached to KB 441333:

253bf30d0b33e0c6640aa6cbdf96de41a4a6d75d0265db269b1f44099308ca4c

Do not run the script if the checksum differs. Download the current attachment again and recheck the KB because Broadcom can replace the attachment and publish a new checksum.

What the Script Does

The LCM component cleanup script enables administrators to manage Day-N deployed components visible in the VCF Operations UI:

  • List components: View all deployed components currently eligible for removal.
  • Delete components: Remove an eligible component record or deployment according to its component type and version. The effect is not the same for every component, so confirm the selected component ID and the relevant KB section before proceeding.

Important notes:

  • If a component is running a version older than 9.1, it is removed solely from the Fleet lifecycle. The script does not delete the corresponding infrastructure deployments such as vCenter or VCF Services Runtime.
  • VSP refers to VCF Management Services.

1. OVA Components

Deleting an OVA-based deployment removes it from Fleet lifecycle and also deletes the associated virtual machines from vCenter.

List Components Deployed on vCenter

python cleanup_component.py list ova-component --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local

Delete Component Deployed on vCenter

python cleanup_component.py delete ova-component --component-id <ova-component-id> --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local --vcenter-username <vcenter-username>

The script will prompt for the required passwords. Once confirmed, the OVA component will be removed from Fleet lifecycle and its associated VMs deleted from vCenter.

2. VCF Management Services (VSP) Components

Deleting a VSP-based deployment removes it from Fleet lifecycle and also deletes the associated deployment from VCF Services Runtime.

List Components Deployed on VCF Services Runtime

python cleanup_component.py list vsp-component --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local

Delete Component Deployed on VCF Services Runtime

python cleanup_component.py delete vsp-component --component-id <vsp-component-id> --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local

3. VCF Automation

VCF Automation is a multi-component deployment consisting of:

  • VCF Automation
  • Migration Service Engine
  • VCF Automation VCF Services Runtime

Important: You must remove VCF Automation and the Migration Service Engine before you remove the VCF Automation VCF Services Runtime. Follow the order below.

Destructive operation: For VCF Automation 9.1, this sequence completely removes the solution. Continue only for permanent removal or a fresh deployment without restoration. It is not supported for VCF Automation upgrade-failure cleanup. Run the entire VCF Automation 9.1 cleanup sequence in this section as the root user inside the SDDC Manager virtual machine.

Step 1: Remove VCF Automation and Migration Service Engine

List Components Deployed on VCF Services Runtime

python cleanup_component.py list vsp-component --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local

Delete Component Deployed on the VCF Automation VCF Services Runtime

python cleanup_component.py delete vsp-component --component-id <vsp-component-id> --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local --vcfa-vcf-services-runtime-fqdn <vcfa-vcf-services-runtime-fqdn> --vcfa-vcf-services-runtime-username <vcfa-vcf-services-runtime-username>

Run the delete command for both the VCF Automation component and the Migration Service Engine component before proceeding to Step 2.

Step 2: Remove the VCF Automation VCF Services Runtime

Warning: Deleting a VCF Services Runtime requires this script to be executed as the root user inside the SDDC Manager virtual machine.

List VCF Services Runtime

python cleanup_component.py list vsp-cluster --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local

Delete VCF Services Runtime

python cleanup_component.py delete vsp-cluster --component-id <vsp-cluster-id> --fleet-fqdn <fleet-lcm-fqdn> --vcf-services-runtime-fqdn <vcf-services-runtime-fqdn> --vcf-services-runtime-username admin@local --vcenter-username <vcenter-username>

Summary

The cleanup_component.py script is a handy workaround for the missing “Delete” option in VCF Operations 9.1. The key things to remember:

  1. Back up and verify any critical component data before running delete operations; do not assume this cleanup can be reversed with a snapshot or restored deployment.
  2. For OVA components, deletion also removes VMs from vCenter.
  3. For VSP components, deletion also removes the deployment from VCF Services Runtime.
  4. For VCF Automation 9.1, cleanup means full removal: do not use it for a failed upgrade or a restore, and use a fresh deployment only when the documented scenario permits it.
  5. Run the entire VCF Automation 9.1 cleanup sequence as root inside the SDDC Manager VM. Delete VCF Automation and Migration Service Engine first, then delete the VCF Services Runtime.
  6. Always verify the script checksum before running it.

After removing components, also check Fleet password management for leftover or expired password accounts. I covered that remediation in Fixing Expired Password Sync in VCF 9.1 Fleet Management.

For the official script download and additional details, refer to Broadcom KB article 441333.

I hope this helps!