Inconsistency Between Aria Automation Orchestrator nodes in showing created MSSQL Database Cluster

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• A user deploys new MSSQL Database Cluster via the Aria Automation Orchestrator plugins using "Add a Database" workflow.

 

• This workflow runs without issue and the database is consistent when ran on a single node Aria Automation Orchestrator.

 

• We see inconsistencies when running this on a Clustered Aria Automation Orchestrator environment where we see a different number of Databases depending on which user we are logged in as and the user session. 

 

• For example: If we deployed 5 Databases using the "Add a Database" workflow in the Aria Automation Orchestrator.
  • For User A in User Session B we see 3 Databases whereas User C in User Session D can see all 5 deployed Databases under the plugin.

Environment

• Aria Automation Orchestrator 8.x

Cause

• Issue in the SQL Plugin code  due to a race condition when a user adds multiple database endpoints in rapid succession via an automated pipeline.

 

• The plugin does not explicitly reload the data after adding the database endpoint and assumes that there is no other node adding at the same time, the last node adding is assuming that it already has the latest version.

Resolution

• Issue fixed in Aria Automation 8.18.1 Patch 3/Aria Automation Orchestrator 8.18.1 Patch 3.