Unable to remove disconnected/standalone secondary manager when multiple managers are configured on primary

Products

• VMware NSX

Issue/Introduction

• Initial removal of a SECONDARY NSX -V manager node fails resulting in it going to a TRANSIT stage
• After the initial issue is resolved and the SECONDARY node is successfully converted to STANDALONE we are unable to remove the disconnected SECONDARY NSX-V Manager from the PRIMARY 
• Multiple SECONDARY managers are configured on the PRIMARY node

ERROR: Remove Secondary NSX Manager failed.

Environment

6.x

Cause

• Error states the UUID of the secondary trying to be removed is no longer present, issue is due to the other secondaries holding stale objects relating to this manager
• Error states the following in VSM.log on the NSX-V Manager:

YYYY-MM-DD 00:00:00.000 GMT  WARN http-nio-127.0.0.1-7441-exec-33 RemoteInvocationTraceInterceptor:88 - Processing of VsmHttpInvokerServiceExporter remote call resulted in fatal exception: com.vmware.vshield.vsm.replicator.configuration.facade.ReplicatorConfigurationFacade.removeNsxManager
com.vmware.vshield.vsm.replicator.configuration.exceptions.ReplicatorException: nsx-replicator-mgmt:160207:NSX Manager with UUID undefined is not registered.; nested exception is org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request: [<?xml version="1.0" encoding="UTF-8"?>
Caused by: org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request: [<?xml version="1.0" encoding="UTF-8"?>
<errors><error><details>NSX Manager with UUID undefined is not registered.</details><errorCode>160207</errorCode><moduleName>nsx-replicator-mgmt</moduleName></error></errors>]

Resolution

1. Identify all of the listed secondary managers
2. Remove any other secondary managers that are not the one in the problematic state, assuming the initial issue is resolved these will remove as expected
3. Confirm all other managers have been removed, once all other secondary managers have been successfully removed, all stale references that reference the problematic secondary manager are also removed
4. Proceed to reattempt removing the problematic secondary manager, as all stale references were removed in step 2, this should proceed to remove as expected.