Error LCMVRAVACONFIG590007 failed to replace new Aria Automation license via Locker.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to replace an Aria Automation (formerly vRealize Automation or vRA) license through Aria Suite Lifecycle (ASL) Locker, the operation fails with error LCMVRAVACONFIG590007. The ASL UI displays the message: "Failed to apply License key. Please check whether the license provided is correct and retry." Additionally, the option to remove the existing license within ASL may be grayed out due to product associations. Further investigation in the logs or error details reveals an EngineException stating: "VMware Aria Automation is already having VCF_ENABLED applied. Add/Replace license operation not allowed if product has VCF/VVF license applied."

Environment

Aria Automation 8.18.x

Aria Suite Lifecycle 8.18.x

Cause

The root cause is the persistent presence of a legacy license key, specifically one that indicates VCF_ENABLED or VVF_ENABLED, within the Aria Automation appliance's local keystore. This occurs even if previous attempts were made to update or remove licenses via the Aria Suite Lifecycle UI. The presence of this hard-coded or locally cached legacy license prevents Aria Suite Lifecycle from performing new license operations (such as Add or Replace). The system incorrectly identifies a conflict, believing a VCF/VVF-enabled license is already active, which then blocks any new license application, leading to the LCMVRAVACONFIG590007 error. This situation can arise when vRA licenses are not fully disassociated locally after updates or changes.

Resolution

To resolve this issue, the legacy license key must be manually removed from the Aria Automation appliance's local keystore. Afterwards, the license management within Aria Suite Lifecycle can be performed successfully.

Steps:

1. Login to the Aria Automation appliance via SSH as root.
2. List all existing licenses to identify the legacy or problematic key:
   vracli license
   Identify the license key corresponding to the VCF/VVF-enabled entry that is causing the conflict.
3. Manually remove the identified legacy license key:
   vracli license remove <license_key>
   Replace <license_key> with the actual problematic license key obtained from step 2.
4. Login to the Aria Suite Lifecycle UI.
5. Trigger an inventory sync for the Aria Automation environment. This ensures ASL's knowledge of the vRA environment is refreshed.
6. Delete the expired or conflicting license from the Locker within Aria Suite Lifecycle (if it still appears there).
7. Proceed with adding or replacing the new Aria Automation license via Aria Suite Lifecycle Locker as intended.