Additional VMDK files are not deleted in vSphere when machines are migrated via Update deployment operations in Aria Automation

Products

• VMware Aria Suite

Issue/Introduction

• Additional VMDK files are not deleted in vSphere when machines are migrated between clusters via an Update deployment operation. Checking the original datastore you can see the vmdk files still present for any additional disks.
• Provisioning service logs show that the disk is detached in Aria Automation before the virtual Machine is removed:

2024-02-12T06:41:46.264Z INFO provisioning [host='provisioning-service-app-77b7b7dbc-hm2md' thread='xn-index-queries-7' user='provisioning-Ao17NlbQN5wTbkjd([email protected])' org='4dd278e8-1b89-4c25-b777-66d5ad7dd716' trace='d2889a7c-314e-4f96-850e-16d78552402a' parent='9467201e-3f15-4b54-bb68-339d349abf6a' span='17c235f3-ed15-41c7-8f72-0049d2dfdaf1'] c.v.a.r.c.ComputeRemovalTaskService.lambda$detachDisks$53:1076 - [/provisioning/requests/compute-removal-operations/8e2763fd-f53c-418d-9882-17e1fa44615a] Creating detach operations for [/resources/disks/3a702fcb-dfd3-4c92-9270-223ed6996d67] that are attached to /resources/compute/9b2cbfd6-f72f-4927-9fff-473a480cf62f

Environment

VMware Aria Automation 8.x

Resolution

This detach operation is what leads to the additional vmdk being left behind along with its parent folder. The detach doesn't happen during a regular machine Delete and only happens during a Machine recreate via an update deployment operation.

The behaviour is a precautionary measure against potential data loss. In certain instances, users may not be aware of the existence of image disks within the deployment canvas, as these disks are internal to the utilized image and cannot be controlled from the deployment canvas.

It is designed to prevent unintentional data loss when update deployment operations are performed which may results in disks being removed.

To workaround the issue you can manually deleted the disks from vCenter.