System halt message during cloud proxy boot.

Products

• VCF Operations
• VMware Cloud Foundation

Issue/Introduction

When attempting to boot a Unified Cloud Proxy (CP) appliance in a VMware Cloud Foundation (VCF) 9.x environment, the virtual machine enters a "Halted" state. You observe the following symptoms:

• The vSphere Console displays the error message: Cloud Proxy system Halted error on boot.
• The appliance is unreachable on the network.
• This behavior typically occurs after the VCF Operations instance has been reverted to a snapshot or upgraded.
• General troubleshooting via Cloud Proxy Troubleshooting fails to resolve the issue.

Environment

VMware Cloud Foundation 9.x

Cause

The Unified Cloud Proxy is designed to halt its own boot process if it detects that it is disconnected or desynchronized from its parent Operations instance.

In this scenario, if the Operations instance is reverted to an older snapshot and then re-upgraded, the management link or security tokens for the Unified Cloud Proxy (which was deployed during the initial convergence process) become invalid. The Cloud Proxy halts the VM to prevent unauthorized or orphaned CPU cycle consumption.

Resolution

To resolve this issue, you must redeploy the Cloud Proxy.

1. Log in to the vSphere Client.
2. Locate and Delete the existing, halted Unified Cloud Proxy VM from the inventory.
3. Navigate to the VCF Operations management interface.
4. Initiate the Cloud Proxy redeployment as part of the standard VCF convergence workflow. Deploy Cloud Proxy as part of a VCF 9.1 Upgrade
5. Once the deployment task completes, verify that the new appliance maintains a "Running" status and is accessible via the network.

This action resolves the issue by establishing a fresh, synchronized management connection between the Operations instance and the Cloud Proxy, clearing the halt state triggered by the previous authentication mismatch.

Additional Information

If you're using Telegraf you may need to follow this kb as well after redeploying the proxy

Telegraf agents are in a non-collecting state after Cloud Proxy redeploy.