Inconsistent cloud accounts listing in a Multi Tenant Aria Automation Orchestrator Inventory under VMware Aria Automation Plugin

Products

• VMware Aria Suite

Issue/Introduction

• In a multi tenant Aria Automation instance, when viewing the orchestrator inventory for a specific tenant from : Aria Automation UI for that tenant >  Orchestrator > Inventory > Aria Automation Plugin added Instances: lists cloud accounts mapped to the other tenant as well. 
• The multi tenancy configuration enforced doesn't permit share resources across tenants. 
• The Issue may be noticed only with specific sets of tenants, the other tenants show data instances in the inventory as expected without showing data from other tenants. 
• Workflows and action items, consume resources - from the VMware Aria Automation plugin inventory - irrespective of tenancy defined boundaries. 

 

Environment

VMware Aria Automation 8.x
VMware Aria Automation Orchestrator 8.x 

Cause

• This may be caused due to the Aria Automation Orchestrator failing to apply the tenancy flag when initializing the orchestrator inventory due to the session per user configuration being used. 
• The inventory may have not refreshed accurately and thus adds in incorrect references

Resolution

This issue can be resolved by refreshing the Aria Automation plugin inventory instances. 

• Navigate to Workflows > Library > vRealize Automation / Aria Automation > Configuration > Update a vRA / Aria Automation Host.
• Click Run
• Select the Aria Automation host mapped to the specific Tenant.
• Ensure the connection type is shared session.
• Validate other properties and click submit.
• Once complete, Refresh the UI.
• Validate that the inventory is now refreshed and shows only required instance mappings. 

Note:

• Refreshing one instance from the Aria Orchestrator's inventory would force the reapplication of the tenancy boundaries and refresh mappings for the specific tenant. 
• The process may have to be repeated once per affected tenant.