Unable to perform config import operation - "Location x is not empty, has x policies an x groups. Please try again after cleaning up the location."

Products

• VMware NSX

Issue/Introduction

• Unable to perform config import operation after LM (Local Manager) is onboarded to GM (Global Manager), received error message below:
  "Location x is not empty, has x policies an x groups. Please try again after cleaning up the location."
• Observed error messages below from Global Manager log (gmanager.log) under /var/log/gmanager/

yyyy-mm-ddThh:mm:ssZ ERROR ClientReceiverFlowHandler-2 GMARDataPostProcessorImpl 4673 POLICY [nsx@6876 comp="global-manager" errorCode="MP500032" level="ERROR" subcomp="global-manager"] Exception encountered while executing resource listeners

java.lang.IllegalArgumentException: Invalid UUID string: 1002057

    at java.util.UUID.fromString(UUID.java:194) ~[?:1.8.0_342]

yyyy-mm-ddThh:mm:ssZ WARN ClientReceiverFlowHandler-2 NsxTRestClient 4673 POLICY [nsx@6876 comp="global-manager" level="WARNING" subcomp="global-manager"] Authentication failure with NSX manager, will retry

org.springframework.web.client.HttpClientErrorException$Forbidden: 403 : "{<EOL> "httpStatus" : "FORBIDDEN",<EOL> "error_code" : 401,<EOL> "module_name" : "common-services",<EOL> "error_message" : "Write operations are temporarily blocked"<EOL>}"

    at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:109) ~[spring-web-5.3.20.jar:5.3.20]

    at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:168) ~[spring-web-5.3.20.jar:5.3.20]

    at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:122) ~[spring-web-5.3.20.jar:5.3.20]

Environment

VMware NSX-T Data Center
VMware NSX

Resolution

This is a known issue impacting VMware NSX.

Workaround:

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.