VSP Cluster status showing unknown

Products

• VCF Operations

Issue/Introduction

• In VMware Cloud Foundation (VCF) 9.1 environments, the VSP Cluster status may display as "Unknown" in the Operations console. This prevents administrators from monitoring the health of components, and the components view may appear broken.
• VSP Cluster status displays as Unknown.
• VCF 9.1 components do not report health status properly.
  
  /usr/lib/vmware-vcops/user/log/adapters/VmspAdapter/VmspAdapter.log

com.broadcom.adapter3.vmsp.client.exception.InvalidResponseException: Invalid response received while obtaining inventory/metrics - {"messages":[{"level":"ERROR","id":"com.vmware.vcfms.api.NotFound","default":"Not Found"}]}


• Additionally, Ops logs indicate that requests directed to fleet-lcm for component /status endpoints return HTTP 404 Not Found errors while base component queries return HTTP 200 OK:
  
  "GET /vcf-operations/plug/fleet-lcm/v1/components/<REDACTED>/status HTTP/2.0" 404

 

Environment

VCF Operations 9.1

Cause

ulk status retrieval fails because a dead or stale OpsLogs cluster (e.g., version 9.0.2) remains in the inventory. The presence of this unreachable endpoint causes the Fleet LCM status checks to fail with 404 Not Found errors, breaking the status pipeline for the entire cluster.

Resolution

1. Verify network reachability between SDDC LCM (sddc-build-service) and the registered VCF Operations for logs cluster address.
2. Restore connectivity and validate that the  VCF Operations for logs  cluster address configuration is accurate and accessible across all required service ports.
3. Confirm that requests to fleet-lcm component status endpoints return HTTP 200 OK and that the VMSP Adapter successfully collects resources without API errors.

Additional Information

Failed component cleanup during VCF 9.1 installation or upgrade