Migration of TCA from 2.3 to 3.x and earlier versions fails if the existing TCA credentials has special characters and vCenter moid mismatch

Products

• VMware Telco Cloud Automation

Issue/Introduction

Migrating from Telco Cloud Automation (TCA) version 2.3 to TCA 3.x fails when TCA-M and TCA-CPs are in different vCenters. Also, vCenter Password has a special characters. Example: &? etc

 

 

Environment

2.x, 3.x

Cause

When the TCA-M and TCA-CP are located in different vCenter servers, the tool caches the inventory, which is shared across the vCenters. As a result, the same MOID could be associated with different entity names. Regarding passwords with special characters, it has been observed that the ovftool requires the password to be encoded when used for the Virtual Infrastructure URL.

Resolution

VMware by Broadcom is aware of the issue and is actively working on a fix that will be included in an upcoming release.

Workaround:

TCA 3.3 or earlier releases, please perform the following steps:

• Login to the Airagap server.
• Exec into the migration container for more details, please refer the documentation: Migrating TCA 2.3.x to TCA 3.2
• cd /migration/vcenter
• Download updated vcenter_util.py.zip attached in the KB > Extract vcenter_util.py and replace/update your existing file.
• cd /migration
• Run migration again.