NSX Manager upgrade pre-check reports the error - "Failed migrations: Calculating effort for AlbControllerOnboardingMigrationTask. Exception during Data migration.".

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

• We are upgrading NSX from version 4.1.0 or 4.1.1 to 4.1.2 / 4.2.x.
• We are using NSX Advanced Load-Balancer (i.e. AVI ALB). It may or may not be actively integrated with NSX Manager.
• In the NSX Manager's /var/log/syslog.log, we may see messages similar to below:
  
  2024-11-15T14:13:01.863Z IT-VCNSXTM-01 NSX 3312 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] [PUC] Finish Upgrade Evaluation Tool execution check on component MP. Result -- BasicInspectionTaskResult{status=FAILURE, taskInfo=InspectionTaskInfo[acknowledgement=false,componentType=MP,description=Prompts user to execute Upgrade Evaluation Tool before proceeding with upgrade.,id=upgradeEvaluationToolCheck,name=Upgrade Evaluation Tool execution check,needsAcknowledgement=false,needsResolution=false,resolution=false,resolutionError=<null>], failureMessages=null, failures=[{"moduleName":"upgrade-coordinator","errorCode":36000,"errorMessage":"NSX Manager upgrade dry run failed. Do not proceed with the upgrade. Please collect the support bundle and contact VMWare GS. Failed migrations: Calculating effort for AlbControllerOnboardingMigrationTask. Exception during Data migration#012"}]}
  
  
• In the NSX Manager's /var/log/upgrade-coordinator/logical-migration.log, we may see messages similar to below:
  
  2024-11-15T14:02:05.938Z WARN pool-13-thread-1 UfoCorfuTableMigrator 1192693 - [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] ERROR while finding effort for logical migration MappingDetails{name='AlbControllerOnboardingMigrationTask', runForTheseFromVersions='3.2.0,3.2.1,3.2.2,3.2.3,4.0,4.1.0,4.1.1', targetVersion='4.1.2', modelName='null', migrationType=null, reason='This migration task will run for migrations from 3.2 to 4.1.2. It will update ALBControllerAdminCreds entity.', customMigratorClassName='com.vmware.nsx.management.migration.impl.AlbControllerOnboardingMigrationTask', fieldMappings=null, targetProtoName='null', requiresCustomCode='false', owner='null', apiToTest='null', weight='1.0', impactedTables='ALBControllerAdminCreds', cleanup='false', enabled'false', diskBacked'false', triggerMode'null', supportsResolve'false', component'null'}

Environment

VMware NSX
VMware NSX-T Data Center

Cause

If the ALB-LCM is newly configured on NSX version 4.1.x, owing to protocol changes, the upgrade pre-check / dry run fails with the above mentioned error. If the configuration is coming from the pre-4.1.x versions of NSX, the upgrade won't encounter this issue.

Resolution

The issue is resolved in NSX version 4.1.2 which, can be downloaded from Broadcom Support Portal.

Alternatively, as a workaround, we can follow the below steps:

1. Run the below command to dump the information from the corfu DB table ALBControllerAdminCreds:
   
   corfu_tool_runner.py -n nsx -o showTable -t ALBControllerAdminCreds > /image/alb-creds.dump
   
   
2. Using API, de-board the ALB-LCM onboarding workflow:
   
   DELETE https://<nsx_manager_ip>/policy/api/v1/infra/alb-onboarding-workflow/LCM
   
   
3. Complete the NSX upgrades.
   
   
4. Using API, onboard the ALB-LCM workflow using the mentioned API body:
   
   PUT https://<nsx_manager_ip>/policy/api/v1/infra/alb-onboarding-workflow
   
   API body in json format:
   
   {
 "owned_by": "LCM",
 "cluster_ip": "<controller-ip>",
 "infra_admin_username": "nsxt-infra-admin",
 "infra_admin_password": "<controller-password>",
 "ntp_servers": [],
 "dns_servers": []
}
   
   Note: Replace the placeholders <nsx_manager_ip>, <controller-ip>, and <controller-password> with actual values. Get value of "infra_admin_password" from the /image/alb-creds.dump file.
   
   

**Note**: In case where TKGi is integrated with this ALB / NSX, the above workaround will break the integration of TKGi and ALB. Though the existing TKGi setup continues to work, no further changes can be made until the ALB-LCM workflow is onboarded. Therefore, in such an integration, we have two options:

• Perform NSX upgrade during scheduled downtime of TKGi environment too (when no further changes can be done to the TKGi environment).
• Raise a support ticket with us stating this KB in the description and mention that this pre-check error is being reported for a TKGi-ALB-NSX integrated environment.