Multiple licenses mapped to Aria Automation post upgrade to 8.18.x.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Post upgrade to Aria Automation 8.18.x, a VCF aware Aria Suite Lifecycle may show multiple licenses mapped for a single instance of Aria Automation.
• vASL UI > Lifecycle Operations > Environment > Aria Automation > under the license section we see multiple licenses applied.
• Viewing the the licenses in locker of Aria Suite Lifecycle, shows the Aria Automation instance mapped as an in use reference for multiple licenses. 
• Upon executing vracli license command in Aria Automation, multiple licenses are listed. 

 

Environment

Aria Automation 8.18,x

Aria Suite Lifecycle 8.18.x

Cause

• This is observed in instances where vRealize license was applied prior the upgrade in a VCF aware vASL managed environment.
• Post Upgrade, as we shift towards the unified license for all components in VCF vSphere, as a part of the VVF licenses, the License is picked up and applied for all components applicable for the licensing and thus post upgrade.
• Thus, we notice that on Aria Automation 8.18.x post upgrade, the active licensing would be changed to vSphere 8 Enterprise Plus Licensing. 
• The same can be validated by running the command: vracli license current 

Resolution

• This scenario is only noticed in case of Aria Automaton is upgraded to 8.18.x and Currently there is no resolution for this scenario.
• This scenario would not be noticed when installing a Aria Automation 8.18 from OVA and if vRealize licensing was selected or applied manually. In such a scenario, the applied license would persist as the active license. 
• To workaround the scenario, manual removal of the old license would be needed. To update stale license from Aria Automation
  1. SSH to the Aria Automation appliance using root credentials. 
  2. List the license currently in active use using the command  :
     vracli license current
  3. List all the license keys using command :
     vracli license 
  4. Identify all the keys which are listed apart from the currently active license. 
  5. Manually, remove the license keys identified in step 4.
     vracli license remove <license key>
  6. Re-run the list command to validate that all unused licenses are removed 
     vracli license 
  7. Trigger an Inventory Sync from vASL to update vASL about the product's license mapping.