VCF Operations Log Management Installation Fails with HTTP 500 Error

Products

• VCF Operations

Issue/Introduction

When attempting to install the Log Management component in VMware Cloud Foundation (VCF) Operations, the installation task fails to initialize or complete. Analysis of the task logs indicates an HTTP 500 internal server error during a GET operation initiated from the Fleet Service node.

The logs show the following failure signature: "method":"GET","protocol":"HTTP/2","response_code":500,"response_code_details":"via_upstream","route_name":"httproute/vcf-fleet-lcm/vcf-fleet-upgrade-service-fleetupgrade-httproute/...","upstream_host":"###.##.#.###:9123"

This indicates a communication failure where the request to the upstream service host (upstream_host) returned an error. This behavior points to a transient communication timeout or handshake failure between the local service and the upstream management component.

Environment

• VMware Cloud Foundation (VCF) Operations 9.1.0
  
  
• Log Management 9.1.0

Cause

The issue is caused by a transient network latency or timing conflict between the Fleet Service node and the management platform during the service initialization request. This results in the upstream service returning an HTTP 500 error, causing the installation task to fail. This is typically an intermittent issue not linked to a persistent configuration error.

Resolution

The recommended resolution is to re-trigger the installation task via the user interface.

Steps:

1. Log in to the VCF Operations console with an admin level account.
2. Navigate to Build ➔ Lifecycle ➔ VCF Management ➔ Tasks (tab).
3. Locate and select the failed Log Management deployment task in the list.
4. Click the Retry button at the bottom of the task window.
   

Workaround

If the Retry action does not resolve the issue, verify the network connectivity between the Fleet Service node and the management cluster hosts. Ensure there are no active network interruptions or high latency conditions in the management network segment before attempting a subsequent retry.

Additional Information

This error is often transient. If the issue recurs frequently despite multiple retries, please collect the VCF Runtime Services support bundle and Contact Broadcom support for log analysis to rule out underlying environmental network issues or service platform degradation.