Attempting to perform HCX vMotion migration fails with error message: java.lang.RuntimeException: Could not resolve segment /infra/segments/hcx-ne-(UUID) to opaque network. Failed to get realized state.
search cancel

Attempting to perform HCX vMotion migration fails with error message: java.lang.RuntimeException: Could not resolve segment /infra/segments/hcx-ne-(UUID) to opaque network. Failed to get realized state.

book

Article ID: 415089

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

Migration using HCX fails during switchover with the following error in the HCX migration tab

vMotion failed. java.lang.RuntimeException: Could not resolve segment /infra/segments/hcx-ne-(UUID) to opaque network. Failed to get realized state. Result: {"status":"failure","statusCode":403,"details":"","result":{"module_name":"common-services","error_message":"The credentials were incorrect or the account specified has been locked.","error_code":403}}


Environment

HCX 4.11 and HCX 9.0

Cause

NSX admin password was changed preventing HCX from communicating to NSX for required steps during switchover, resulting in a migration failure.

Resolution

  1. Ensure you have the correct NSX admin password and are able to login to all of the NSX managers in the NSX cluster with this account
  2. Login to HCX VAMI page in the Target/Destination Cloud environment (https://<hcx-manager.fqdn>:9443) using the HCX admin user account
  3. On the HCX Dashboard, Click "Manage" for the NSX Tile, then Click "Edit"
  4. Update the NSX admin account credentials and click "Save"
  5. Go to the "Appliance Summary" tab and restart  "Migration Planning Service", "Web Service" and "App Service" Services (or reboot the HCX appliance). Click "Stop", then click 'Start" when available.
    1. Start with "Migration Planning Service" first. 

Additional Information

There might be a potential for NSX API to lock out HCX error; 

Please see the following KB article for additional information:
HCX Service Mesh Alterations, Migrations, or update of integrated NSX account credentials fail due to NSX-T API Authentication failure