Unable to migrate a workload cluster from the existing management cluster to a new management cluster.

Products

• VMware Telco Cloud Automation
• VMware Telco Cloud Platform

Issue/Introduction

When attempting to migrate (rehome) a workload cluster from an existing source management cluster to a new target management cluster in VMware Telco Cloud Automation (TCA), the migration fails during the validation phase.

The system displays the following error indicating that the required TcaBomRelease is missing on the target management cluster:

[ E_INVALID_INPUT ] TcaBomRelease tbr-bom-<version> does not exists on target management cluster <target-mgmt-cluster-name>

Additionally:

• Manually attempting to create the missing TcaBomRelease on the destination management cluster shows the BOM as incompatible during the migration.

• The TCA UI shows that the workload cluster is operating on the newer/correct BOM release (e.g., 25177740), but the rehome validation insists on looking for the older BOM release (e.g., 24420202).

Environment

TCA 3.x, TCP 5.x

Cause

This issue occurs due to a state mismatch between the TCA UI and the underlying control plane Custom Resource (CR) of the workload cluster.

While the node pools may have successfully updated to the new BOM, the control plane CR is stale and still references the old tcaBomRelease. Because the target management cluster only contains the new BOM, validation fails when it attempts to verify the presence of the stale BOM version referenced by the control plane CR.

"tcaBomRelease": "tbr-bom-2.3.0-v1.24.10---vmware.1-tkg.2-tca.24420202",
"totalReplicas": 3,
"updatedReplicas": 3

(In this scenario, the CR reflects 24420202, even though the TCA UI correctly displays 25177740)

Resolution

To resolve this issue, you must force a state reconciliation on the workload cluster's control plane so that the backend CR matches the correct BOM version displayed in the UI.

Steps to Remediate:

1. Verify the Mismatch: Confirm the discrepancy by checking the control plane CR on the source workload cluster. Compare the tcaBomRelease value in the CR against what is displayed in the TCA UI.

2. Perform a "Dummy" Edit: Log into the TCA UI, navigate to the affected workload cluster, and edit the control plane configuration. Perform a non-disruptive "dummy" edit (such as adding and then removing a tag, or simply opening the edit wizard and saving the configuration without making functional changes).

3. Verify the CR Update: Check the control plane CR again via the CLI to ensure the tcaBomRelease has updated to the correct, current BOM version.

   kubectl get tcabomrelease -A
   

4. Retry the Migration: Once the CR reflects the correct BOM (e.g., 25177740), retry the rehome operation. The pre-validation should now pass successfully, allowing the co