NSX Host Transport Nodes Missing from VCF Operations Inventory

Products

• VCF Operations

Issue/Introduction

• Workload domain NSX Host Transport Nodes are not populating within the VCF Operations inventory.
  
  
• Management domain nodes and Workload domain Edge Transport Nodes display normally without issue. 
  
  
• Manual inventory sync and stopping/starting metric collection do not resolve the missing host transport nodes.
  
  
• The NSX Adapter logs show no specific entries for the Host Transport Nodes, but record the following policy API exception regarding enforcement points:
  Collector's log directory: adapter/NSXTAdapter/NSXTAdapter_ID.log
  

  [DATE/TIME] ERROR NSXTAdapter #### [ops@#### threadId="######" threadName="NSX-T Metric Collector thread #, time: ### ### ## ##:##:## UTC ####" instanceId="####"] [(####) com.vmware.adapter3.nsxt.util.NsxtApiUtil.queryData] - Error in fetching response for query : LB Pool Status Query , exception caused is: com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) (statusCode:400) =>
  { messages = [], data = => {error_message=The requested runtime information cannot be retrieved for all EnforcementPoints because there is no support to get the specific runtime information for [/infra/sites/default/enforcement-points/alb-endpoint]. Please try the API with specific enforcement_point_path that supports such runtime information., httpStatus=BAD_REQUEST, error_code=500276, module_name=Policy}
  ,
  errorType = INVALID_REQUEST
  }

Environment

VCF Operations 9.0.2

Cause

The issue occurs because querying unsupported enforcement points (e.g., alb-endpoint) causes an API failure that interrupts the NSX-T adapter's metric collection thread,

preventing the inventory synchronization for Host Transport Nodes.

Resolution

There is currently no workaround for this behavior.

A fix for this issue will be included in a future General Availability (GA) release