vRNI Node Group Profiles Failing Promotion from Manager to Policy

Products

• VMware NSX

Issue/Introduction

An error occurs when attempting to promote two vRNI Node Group profiles from Manager to Policy objects within NSX. The migration process fails to complete for both profiles.

When reviewing the migration task, the failures can be verified by the following specific error messages:

• Profile 1: 

  vRNI-Node_Group_Profile_RFFVMzlNTw==
  The requested object : /infra/domains/default/groups/########-####-####-####-#######7aa1d could not be found. Object identifiers are case sensitive.

• Profile 2:

  vRNI-Node_Group_Profile_RFFVMzlNTw==
  Group with id ########-####-####-####-#######7cc4 cannot be migrated as transport node ########-####-####-####-#######90ac is not found.

Environment

VMware NSX

Cause

The migration engine fails due to the presence of stale object references within the NSX Node Groups.

Specifically, the second profile contains a stale, "phantom" transport node that displays an NSX UUID rather than a standard host FQDN. Because this referenced transport node does not actually exist in either the NSX or vCenter inventories, the migration engine cannot locate it to successfully process the promotion.

Resolution

To resolve this issue, you must use the NSX API to bypass UI limitations and manually excise the stale host object from the group.

Follow these steps to clear the stale references and successfully promote the recoverable profiles:

1. Retrieve the Group's Configuration: Use a GET API call to retrieve the current configuration payload of the affected NS-Group.

   • GET https://<nsx-mgr>/api/v1/ns-groups/{ns-group-id}

2. Modify the JSON Payload: Copy the output from the GET request into a text editor. Locate and manually delete the block containing the stale transport node object.

3. Push the Modified Payload: Push the updated JSON configuration back to the NSX Manager using a PUT API call to the exact same endpoint.

   • PUT https://<nsx-mgr>/api/v1/ns-groups/{ns-group-id} 

   • Note: Ensure you receive a 200 OK response from the server, which confirms the invalid reference has been successfully removed.

4. Re-run the Promotion: Return to the NSX UI and re-run the Manager to Policy promotion task.

   • The successfully altered profile (Profile 2) should now migrate without issue.

   • For the irreparably broken profile (Profile 1), select "skip and continue" when prompted.

5. Cleanup: To ensure the environment is left clean, synchronized, and free of orphaned objects, manually delete the remnants of the unfixable failed Node Group profile (Profile 1) from both the Manager and Policy UI views.

Additional Information

Please perform Manager to Policy promotion error during upgrade to VCF 9

NSX Federation Environment: vRNI Groups Enter Failed State After Brownfield Configuration Import