Error: 500 INTERNAL_SERVER_ERROR during Cloud Proxy installation in VCF Operations

Products

• VCF Operations

Issue/Introduction

VCF 9.1 Greenfield Fleet deployment fails when using an existing Aria/VCF Operations 9.1.0 instance. The failure occurs during the subtask to install the VCF Cloud Proxy using the Fleet Lifecycle task. This typically happens when the existing operations instance is on a different network than the management vCenter.

Deployment fails at subtask: "Install VCF Cloud Proxy using Fleet Lifecycle". The UI displays the following error:

The Fleet lifecycle 'Update component' task with ID <Task ID> failed.
Internal errors: Task with ID <Task ID> from SDDC lifecycle with ID <Request ID> has completed with failure(s). Check the errors in the next sub-task(s) for more details., Failed to start task (error may be truncated): Unexpected HTTP response (Reference ID: ABCDEF) - Status: 500 INTERNAL_SERVER_ERROR,
reason: Unable to resolve the placement for component with ID <Component ID>.,
resolution: Check server logs for details.

Environment

VCF Operations 9.1 

Cause

The deployment fails because the existing VCF Operations instance is located on a different network or vCenter than the management vCenter. The "Deploy New Fleet" workflow assumes VCF Operations resides in the management vCenter; when it does not, placement resolution fails.

Resolution

This behavior is under review and will be addressed in the upcoming VCF Operations release.

The planned enhancement will automatically select the corresponding vCenter when an existing VCF Operations instance is chosen. The workflow will then validate that the VCF Operations VMs are located within that vCenter and prevent deployment until the correct vCenter is provided.

To receive updates on the fix status, please subscribe to this article (Reference: Article 275360).

Workaround:

As the failure occurs during the deployment phase, there is no way to migrate VCF Operations before starting the deployment. To bypass this issue, perform the following steps:

1. Allow the initial deployment task to fail in the UI.

2. Migrate the existing VCF Operations VMs to the management vCenter.

3. Retry the failed deployment task.