Cluster Move/Rehome Issue for Clusters Created on or Before TCA 1.9
search cancel

Cluster Move/Rehome Issue for Clusters Created on or Before TCA 1.9

book

Article ID: 409844

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

Cluster Move/Rehome Precheck Behavior (IP Family Mismatch)

The move/rehome process includes prechecks to ensure the workload cluster's associated management cluster aligns with the target management cluster. One key parameter validated is the IP Family, which defines the IP stack used.

If the source and target management clusters have mismatched IP Families, the move is blocked.


Important Note:

  1. Move is allowed only when the source and target management clusters have the same IP Version — for example, both must be either IPv4 or IPv6.
  2. Management clusters created in or before TCA 1.9 and later upgraded may not have the IP Family field set (shown as IP Version in the UI). In such cases, the UI marks the source management cluster’s IP Family as "unknown", which disables the Move button.
  3. During the move wizard in the TCA UI, a message is displayed if there's an IP Family mismatch, and the Move button is disabled

Environment

  • TCP 4.0
  • TCA 3.1

Resolution

  1. Identify the workload cluster to move and determine its associated management cluster.

  1. Verify the IP Version of the associated management cluster.

 

  1. In a typical scenario where the IP Version matches between the source and target management clusters, the move wizard displays the following details and the 'Move' button is enabled.

 

  1. If the IP Version field is missing or shows 'unknown', apply the following steps to apply the workaround.

 

Workaround:

  1. Open the browser's developer tools. (See Figure)





  2. Click on the icon in the top left corner of the developer tools (refer to the red line in Figure).





  3. Click the button in front of the disabled cluster. This will allow you to see the corresponding HTML component in the developer tools. Make sure you see the combination of clr-radio-wrapper, input, and label. Then, delete the disabled attribute after the input component (refer to the red line in Figure).