VCF Operations Fleet Manager's UI is unresponsive with HTTP 504 and Authorization failures

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• In VCF Operations 9.x, the Fleet Management UI becomes unresponsive, leading to intermittent HTTP 504 Gateway Timeouts and Authorization failures. Users may observe that specific administrative menus, such as Certificates and Passwords, fail to populate or disappear entirely.
  
  

Error in /var/log/vmware_vrlcm.log of the Fleet Manager

####-##-##T##:##:##.###Z ERROR vrlcm[1278] [pool-3-thread-35] [c.v.v.l.p.c.v.t.BaseConfigureVropsTask]  -- address may be invalid <fleetManager fqdn.com>
####-##-##T##:##:##.###Z INFO vrlcm[1278] [pool-3-thread-35] [c.v.v.l.d.v.VropsConnector]  -- url to connect https://<fleetManager fqdn.com>/casa/authorize

####-##-##T##:##:##.###Z ERROR vrlcm[1278] [pool-3-thread-35] [c.v.v.l.p.c.v.t.BaseConfigureVropsTask]  -- address may be invalid <fleetManager fqdn.com>
####-##-##T##:##:##.###Z INFO vrlcm[1278] [pool-3-thread-22] [c.v.v.l.d.v.VropsConnector]  -- url to connect https://<fleetManage fqdn.com>/casa/authorize

Environment

• VCF Operations 9.x

Cause

The issue is caused by a failure in the API handshake between management components. Specifically:

1. DNS Misconfiguration: The DNS search suffix in /etc/resolv.conf was incorrectly set to search ., causing Java-based connection tasks to fail or timeout.

2. API Handshake Failures: Repeated 401 Unauthorized errors occurred when attempting to clear stale sessions via the CASA (Cluster and Slice Administrator) API, preventing the retrieval of the "Master Config" required for the UI

Resolution

 

1. Correct DNS Search Suffix:

   1.  SSH into both the VCF Operations and Fleet Management appliances.

   2. Update the DNS Search Domain from . to your correct enterprise domain (example.com).

   3. Verify the change in /etc/resolv.conf.

2. Service Restart :

   1. If the UI remains unresponsive , restart the management services on the fleet manager via SSH:

      systemctl restart vrlcm

3. The fleet Management UI should now be responsive.

 

Additional Information

For detailed steps on reconfiguring environment settings, refer to the Broadcom TechDocs: Reconfigure DNS and Domain Search on VCF Operations Fleet Management.