NS Group member VMs are not showed in the member list.

Products

• VMware NSX

Issue/Introduction

• Some VMs that are expected to belong to an NS group are not displayed in the member list.
• Membership criteria for problematic VM's was based on the computer name.
• Unable to see these VM's in API call output of GET /api/v1/fabric/virtual-machines. 
• In NSX-T inventory UI, there are some virtual machines which is displayed as "Stopped" even though it's powered on

 

 

• From Corfu DB can see these VM's are showing the powered state as stopped.

Run as root on NSX Manager: 
/opt/vmware/bin/corfu_tool_runner.py -n nsx -o showTable -t VmPropertiesMsg

Payload:
{
  "discoveredResource": {
    "displayName": "#####m11",<==== Check the VM name.
    "lastSyncTime": "1724201423581",
    "externalId": "########-####-####-####-############"
  },
  "hostLocalId": "227",
  "computeIds": {
    "moIdOnHost": "227",
    "hostLocalId": "227",
    "locationId": "",
    "instanceUuid": "########-####-####-####-############",
    "externalId": "########-####-####-####-############",
    "biosUuid": "########-####-####-####-############"
  },
  "virtualNetworkInterface": [{
    "uuid": {
      "left": "###################",
      "right": "###################"
    }
  }, {
    "uuid": {
      "left": "###################",
      "right": "###################"
    }
  }],
  "virtualMachineType": "VIRTUAL_MACHINE_TYPE_REGULAR",
  "powerState": "VM_POWER_STATE_TYPE_VM_STOPPED", <================= ****
  "host": "########-####-####-####-############",
  "source": "########-####-####-####-############",
  "biosUuid": {
    "left": "###################",
    "right": "###################"
  }

 

• If click the "SAVE" on it's Edit screen without any change, then the following 500068 error is shown.

Error occurred while executing request on enforcement point path=[/infra/site/default/enforcement-point/default]: can't parse argument number: "httpStatus" : "NOT_FOUND".("error_code" : 500068)

 

• In cm-inventory log, the following error is recorded.

2023-01-30T02:37:07.013Z  INFO http-nio-127.0.0.1-7440-exec-28 LoggingRestTemplate 4205 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-####-####-####-############" subcomp="manager" username="admin"] Request::URI:http://localhost:7443/cm-inventory/api/v1/fabric/virtual-machines?action=update_tags method:POST
2023-01-30T02:37:07.067Z ERROR http-nio-127.0.0.1-7440-exec-28 InventoryRestClientImpl 4205 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP7044" level="ERROR" reqId="########-####-####-####-############" subcomp="manager" username="admin"] Error in rest call url= /cm-inventory/api/v1//fabric/virtual-machines?action=update_tags , method= POST , response= {
  "httpStatus" : "NOT_FOUND",
  "error_code" : 600,
  "module_name" : "common-services",
  "error_message" : "The requested object : ########-####-####-####-############ could not be found. Object identifiers are case sensitive."
} , error= [{"errorMessage":"The requested object : ########-####-####-####-############ could not be found. Object identifiers are case sensitive.","errorData":{"moduleName":"common-services","errorCode":"600","statusCode":"NOT_FOUND"}}]
org.springframework.web.client.HttpClientErrorException$NotFound: 404 : "{<EOL>  "httpStatus" : "NOT_FOUND",<EOL>  "error_code" : 600,<EOL>  "module_name" : "common-services",<EOL>  "error_message" : "The requested object : ########-####-####-####-############ could not be found. Object identifiers are case sensitive."<EOL>}"
        at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:113) ~[?:?]
        at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:168) ~[?:?]
        at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:122) ~[?:?]
        at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) ~[?:?]
        (...snip)

 

Environment

Earlier than NSX-T 3.2.3

Cause

During vMotion of a VM, this issue can occur due to a race condition in threads updating the DB state on the source and destination hosts resulting in incorrect updates to the DB state.

Resolution

This issue is resolved in NSX-T 3.2.3 and later releases.

As a temporary workaround, change the group membership criteria from "Computer Name" to "Name", and the virtual machine will then appear as a member of that group.

For resolving the inventory screen display issue, please contact Broadcom support