Failure to delete additional GCP disks in Aria Automation 8.18.1 deployments

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to remove an additional (non-boot) Google Cloud Platform (GCP) disk from an Aria Automation deployment via the "Remove Disk" Day 2 action, the deletion request fails. Although the disk may be removed from the GCP VM endpoint, it remains visible in the Aria Automation deployment schema and resource tree.

Symptoms:

• Users are unable to delete non-boot GCP disks through the Aria Automation UI or API.
• Deployment deletion fails due to stale disk records that were not properly cleaned up.
• The following error can be seen in /services-logs/prelude/tango-blueprint-service-app/file-logs/tango-blueprint-service-app.log
  

  2025-10-13T11:52:02 tango-blueprint-service-app ERROR tango-blueprint [host='tango-blueprint-service-app-##########-#####' thread='tasks-#####' user='###' org='########-####-####-####-############' blueprint='########-####-####-####-############' project='########-####-####-####-############' deployment='########-####-####-####-############' request='########-####-####-####-############' flow='########-####-####-####-############' task='########-####-####-####-############' tile='########-####-####-####-############' resourceName='' operation='' trace='################################'] com.vmware.tango.blueprint.provider.ResourceTileService - delete request Failed: java.lang.IllegalArgumentException: GCP disk with diskLink: /resources/disks/########-####-####-####-############, cannot be deleted. Current status is ATTACHED

Environment

• VMware Aria Automation 8.18.1
• Cloud Account: Google Cloud Platform (GCP)

Cause

The issue can occur due to a race condition between the disk detach and delete actions.

Resolution

This issue is resolved in upcoming Aria Automation 8.18.1 Patch 5. 

Workaround: For environments where Patch 5 cannot be immediately applied, the "Detach" process must be manually sequenced or programmatically validated within the workflow to ensure the disk transitions to an AVAILABLE or DETACHED state prior to executing the delete action.