Onboarding Plan "Error" Status and Deployment Failures in VMware Aria Automation

Products

• VMware Aria Suite

Issue/Introduction

When running an onboarding plan that includes a large number of deployments, the status of the plan shows as "Error" after just a few seconds of execution. This prevents any deployments from being created, and no machines are onboarded. Upon further inspection, the Machines tab indicates the machines are in a "Pending" state, but no further details are provided in the user interface.

ERROR relocation [host='relocation-service-app-xxxxxxxx-sgrct' thread='xn-index-updates-2'] c.v.relocation.RelocationSpringHost - Created/updated report '/relocation/onboarding/validation-report/xxxxxx-xxxx-xxxx-xxxx-xxxxxxx' for '/relocation/onboarding/deployment/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx'. Messages: Deployment name 'xxxx' is already in use.

Environment

VMware Aria Automation 8.x

Cause

The root cause of the error typically stems from one or both of the following:

1. Duplicate Deployment Names: The presence of duplicate names in the deployment configuration can cause a conflict during the onboarding process.

2. Non-existent Resources: Some resources referenced in the onboarding plan may no longer exist or may have been deleted, causing failures in the execution.

Resolution

To resolve this issue and successfully execute the onboarding plan, follow these steps:

1. Check for Duplicate Deployment Names:

   • Review the deployment configurations in your onboarding plan for any names that may have been reused.

   • If any duplicates are found, change the names to unique identifiers and ensure there are no conflicts.

2. Ensure Resources Exist:

   • Verify that all resources referenced in the onboarding plan (e.g., machines, environments) exist and are accessible. If any resources have been deleted or moved, remove them from the onboarding plan or update the plan with the correct resources.

3. Remove Invalid Entries:

   • Any entries referring to resources that no longer exist or are unreachable should be removed from the plan.

   • Clean up any old or invalid references that might be causing the execution to fail.

4. Retry the Onboarding Plan:

   • Once the conflicting deployment names and invalid resources have been corrected, retry the onboarding plan.

By resolving these issues, the onboarding plan should be able to execute successfully, creating the necessary deployments and onboarding the machines.