Deployment of vRealize Automation 8.0 from Lifecycle Manger fails with the error code: LCMVRAVACONFIG590003
search cancel

Deployment of vRealize Automation 8.0 from Lifecycle Manger fails with the error code: LCMVRAVACONFIG590003

book

Article ID: 314791

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
When deploying vRealize Automation 8.0 from vRealize Suite Lifecycle Manager, the install fails at Initializing vRA with the error code: LCMVRAVACONFIG590003.

If the issue is caused by vRO root password failures (see KB 76870 ) you will also see the following errors in the app-vco-app logs:
ERROR: Unable to configure database.
Error from server (BadRequest)" container "vco-server-app" in pod "vco-app-<UID>" is waiting to start:  PodInitializing.

Environment

VMware vRealize Automation 8.x

Cause

This can be caused by configuration of the CEIP(VMware Customer Experience Improvement Program) or by a failure in the deployment of vRO within the vRA appliance.

Resolution

VMware is aware of this issue.

A resolution for this issue is being evaluated for inclusion in a future release.

Workaround:

To work around the CEIP issue:

Disable CEIP:
  1. SSH into the vRealize Automation appliance (primary or first deployed node).
  2. Confirm the current state of CEIP by running the command:  vracli ceip status
  3. Disable CEIP by running the command:  vracli ceip off
Restart vRealize Automation services:
  1. Restart services by running the command:  /opt/scripts/deploy.sh
Retry the deploy from vRealize Suite Lifecycle Manager:
  1. From the Lifecycle Manager interface, retry the stalled installation of vRealize Automation.

To work around the vRO issue:

Follow the workaround instructions in KB 76870.