NSX-V to NSX-T migration fails when NSX-V application service name has parenthesis in the name
search cancel

NSX-V to NSX-T migration fails when NSX-V application service name has parenthesis in the name

book

Article ID: 367359

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Attempting a NSX-V to NSX-T migration using the Migration coordinator fails with the error: 

Config migration failed [Reason: HTTP Error: 400: Found errors in the request. Please refer to the related Errors for details. for url: http://localhost:7440/nsxapi/api/v1/infra/domains/default/security-policies/<ID>]

The following error is noted in /var/log/migration-coordinator/v2t/cm.log:

ERROR  Failed to PATCH http://localhost:7440/nsxapi/api/v1/infra/domains/default/security-policies/<ID> with status: 400 and reason: {
  "httpStatus" : "BAD_REQUEST",
  "error_code" : 500060,
  "module_name" : "Policy",
  "error_message" : "Found errors in the request. Please refer to the related Errors for details.",
  "related_errors" : [ {
    "httpStatus" : "NOT_FOUND",
    "error_code" : 500090,
    "module_name" : "Policy",
    "error_message" : "Policy object path=[/infra/services/Test_%28Service%29] does not exist."
  } ]
}

Cause

This issue is caused by the NSX-T migration coordinator incorrectly interpreting parenthesis characters

Resolution

This issue is resolved in NSX-T 3.2.4

As a workaround, the parenthesis characters can be removed from the source NSX-V application service name and then retry the V2T migration.