The Machine Association on the disk object gets removed immediately on deployment in Aria Automation when disk is added using the custom day 2 action.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Navigating to Aria Automation UI > Service Broker > Deployments > Deployment Name shows the disk is attached; however, the Machine Association is removed immediately.

• The missing Machine Association on the disk object can result in inconsistent inventory and resource tracking. Additionally, the out-of-the-box Remove Disk action may fail for these disks, leaving orphaned disk resources in the environment.

  This can lead to:

  • Storage resource wastage
  • Increased administrative overhead for manual cleanup
  • Accumulation of stale or orphaned resources over time

• The default out-of-the-box (OOB) Add Disk action is not user-centric and does not automatically honor defined storage constraints unless the user manually specifies the required storage tag.

• As a result, the disk provisioning request may select an unintended or random storage profile instead of placing the disk on the expected storage.

 

Environment

Aria Automation 8.18.x

Cause

A custom script Add Virtual Disk is configured as a Day 2 action in Aria Automation.

This script acts as a wrapper around the out-of-the-box (OOTB) Add Disk action and internally invokes the Add Disk action.

The Machine Association fails when the OOTB Add Disk action completes before the custom Add Virtual Disk action. The association succeeds when the Add Disk action completes after the custom action.

The issue occurs due to a wait condition configured in the Add Virtual Disk workflow, which places the workflow execution on hold. This causes the Machine Association update to be overwritten.

Removing the wait condition allows the workflow to complete successfully and preserves the Machine Association.

Resolution

This fix is scheduled to be included and delivered in one of the upcoming patch release.

To review, analyze & resolve this issue, please contact Broadcom Support and open a support case referencing KB 444397.