You've reached the limit of allowed instances for VCF Operations (maximum: 1)" when connecting VCF Operations to Fleet Management

Products

• VCF Operations

Issue/Introduction

 

• Attempts to connect the VCF Operations cluster to the Fleet Management appliance via the VCF Operations Admin UI fail.

• The /var/log/vrlcm/vmware-vrlcm.log on the Fleet Management appliance displays the following exception:

• com.vmware.vrealize.lcm.lcops.common.exception.InvalidEnvironmentException: Deployment or Import Blocked: You've reached the limit of allowed instances for VCF Operations (maximum: 1)

 

Environment

VCF Operations 9.0x

VCF Operations 9.1.x

Cause

This issue occurs due to a compounding series of state inconsistencies, typically following a failed upgrade or manual disconnection attempt:

Queue Lock: An orphaned VCF Operations for Logs component integration is stuck in a failed state within the Fleet Management appliance. This orphaned record maintains a lock on the lifecycle orchestration queues, blocking the core VCF Operations component from processing a new registration payload.

Credential Desynchronization & Broken Trust: An expired Fleet Manager OS root password or mismatched internal admin tokens cause standard deletion or cleanup payloads to be rejected by the cluster, preventing graceful removal of the orphaned records.

Resolution

To resolve this issue, you must forcefully delete the orphaned VCF Operations for Logs component to clear the lifecycle queue lock, bypassing standard validation checks. 

1. Enable and access the standalone Fleet Management UI.
(Note: If the UI is disabled, SSH into the Fleet Management appliance as root and run touch /var/lib/vrlcm/UI_ENABLED)

2. Log in to the Fleet Management UI and navigate to Lifecycle > VCF Management > Components.

3. Locate the VCF Operations for Logs component record.

4. Click the vertical ellipses (three dots) next to the component and select Delete.

5. Critical: In the deletion prompt, you must set the Skip Validation parameter to True.
(Note: This forces the engine to drop the local database record without attempting to authenticate against the broken upstream cluster).

6. Ensure Delete from vCenter is unchecked/disabled so you do not accidentally delete the actual VCF Operations for Logs virtual machines.

7. Submit the request and wait for the deletion task to complete successfully.

8. Once the queue is successfully cleared, return to the VCF Operations Admin UI and initiate a fresh connection to the Fleet Management appliance. The connection payload should now process successfully.

Additional Information

 

Additional errors observed in the vmware-vrlcm.log may include:

• • LCMVROPCONFIG20001 (Invalid Operations master address)

  • LCMVROPSYSTEM25093 (Credential desynchronization)

  • LCMVROPSYSTEM30023 (Unauthorized access)

  • The Fleet Management component deletion API fails with 401/403 or Unauthorized Access errors.

Related information:

 

• KB 431560: Fleet Management node disconnected in VCF Operations

• KB 422906: VCF Fleet Manager root account disconnected due to password expiration

• KB 432956: VCF Operations for Logs deployment/deletion fails with Unauthorized access (LCMVROPSYSTEM30023)