Unable to delete VIM in TCA UI due to E_OPERATION_FAILED dependencies

Products

• VMware Telco Cloud Automation
• VMware Telco Cloud Platform

Issue/Introduction

While attempting to delete or unregister a Virtual Infrastructure Manager (VIM) (such as a TKG Workload or Management cluster) from the VMware Telco Cloud Automation (TCA) UI, the operation fails with one or both of the following errors:

• E_OPERATION_FAILED: This VIM is currently being used by one or more Network Function (NF) instances. All instances deployed on this VIM must be deleted before the VIM can be removed.
• E_OPERATION_FAILED: This VIM is associated with one or more repositories. The repository associations must be removed before the VIM can be deleted.

Environment

TCA 3.3

TCP 5.0.1 

Cause

TCA maintains logical hooks to the VIM registration to ensure lifecycle management integrity. A VIM cannot be removed if:

1. Active Workloads: There are still Cloud-Native Network Functions (CNFs) or Virtual Network Functions (VNFs) instantiated and tracked in the TCA inventory for that VIM.
2. Partner Repositories: The VIM is still synchronized with partner repositories (such as Harbor or Helm registries) used for workload deployments.

Resolution

To safely delete the VIM, you must systematically remove these dependencies in the following order:

Step 1: Identify and Remove Network Function (NF) Instances

1. Log in to the Telco Cloud Automation (TCA) Manager UI.
2. Navigate to Network Functions > Inventory.
3. Use the filter bar to search for the specific VIM Name that you are attempting to delete.
4. If any NF instances appear in the list:
   • Select the instance and click Terminate. Wait for the task to complete.
   • After termination, select the instance again and click Delete to remove it from the TCA inventory.

Step 2: Unbind Repository Associations

1. In the TCA UI, navigate to Infrastructure Content > Repositories.
2. Alternatively, go to Virtual Infrastructure > VIM Management, select the target VIM, and look for the Associated Repositories or Partner Repositories tab.
3. Identify any repositories (e.g., Harbor) that are still bound to this VIM.
4. Select the association and click Remove Association or Unbind.
   • Note: This does not delete the actual repository server, only the link to this specific VIM.

Step 3: Unregister the VIM

1. Once all NFs are deleted and repositories are unbound, navigate to Virtual Infrastructure > VIM Management.
2. Select the TKG VIM.
3. Click Unregister or Delete. The operation should now complete without the dependency errors.