Troubleshooting TMC Self-Managed Deployment Issues in VCD: Part II

Welcome back to another troubleshooting post for TMC self-managed deployment in VCD. In the previous post, I discussed how to fix the issue of deploying TMC self-managed and publish the solution to tenants. However, there’s another issue that you might encounter when publishing the solution to tenants, which is the task getting stuck during the process. In this post, I will guide you through the steps to troubleshoot and resolve this issue.

Before we begin, please note that these steps are for troubleshooting purposes only and should not be performed in a production environment without consulting the GSS team first.

Step 1: Obtain VCD Auth Token

To start troubleshooting, you need to obtain an auth token from VCD. You can do this by executing the following command in your terminal or command prompt:

vcd-auth login –org –user

Replace with your organization name and with your VCD username.

Step 2: Fetch TMC-SM Solution Add-On Instance UUID

Once you have obtained the auth token, execute the following command to fetch the UUID of the TMC Self-Managed solution add-on installed in your VCD environment:

vcd-api –auth-token call /api/v1/solution-addons?q=tmc-sm

In the response output, locate the UUID of the TMC Self-Managed solution add-on.

Step 3: Update ACL of Entity with VCD System Admin User

Next, you need to update the ACL (Access Control List) of the entity with the VCD System Admin user. To do this, execute the following command:

vcd-api –auth-token put /api/v1/entities/{entity_id}/acl –body ‘{“entity”: {“uuid”: “{entity_uuid}”,”type”: “solution-addon”, “status”: “READY”}}’

Replace {entity_id} with the ID of the entity you want to update, and {entity_uuid} with the UUID of the TMC Self-Managed solution add-on.

Step 4: Get Solution Add-On Instance with Encryption Key

Now, execute the following command to get the solution add-on instance with its encryption key:

vcd-api –auth-token get /api/v1/solution-addons/{solution_addon_id}?fields=encryptionKey

Replace {solution_addon_id} with the ID of the solution add-on instance you want to retrieve.

Step 5: Update Payload with Entity Status and Patch

In the response output of the above API call, ensure that the encryption key is not “******” but has an actual value. If it has an actual value, proceed to update the payload with entity status and patch. You need the full JSON that you obtained in response output.

To update the payload, execute the following command:

vcd-api –auth-token put /api/v1/entities/{entity_id}/patch –body ‘{“op”: “replace”, “path”: “/status”, “value”: “READY”}’

Replace {entity_id} with the ID of the entity you want to update, and {entity_uuid} with the UUID of the TMC Self-Managed solution add-on.

That’s it! By following these steps, you should be able to troubleshoot and resolve the issue of the task getting stuck during publishing of the TMC Self-Managed solution to tenants in VCD. Remember to consult the GSS team before performing any actions in a production environment.