Onboarded VM Disk Records Marked as Missing After Reconciliation in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In environments migrated from vRealize Automation 7.x to Aria Automation 8.x, where clients have onboarded large numbers of VMs (e.g., over 12,000), an issue may occur during disk reconciliation. Specifically:

• Onboarded VMs (not attached to a cloud template) may have their disk records incorrectly marked as missing during reconciliation.

• This occurs even though the VMs and associated disks are present and functional in the environment.

• When comparing results from /deployment/api/deployments/{deploymentId}/resources for both deployed and onboarded VMs, a gap may be observed for onboarded disk records.

Environment

Aria Automation 8.18.1 and earlier 

Cause

This issue is due to a bug in the disk reconciliation process:

• The reconciliation logic uses the isDiskManaged() method, which filters disk records based on the disk's origin.

• The method only considers disks with the origin set to DEPLOYED, and filters out those with the origin ONBOARDED.

• As a result, disks with the origin ONBOARDED are incorrectly identified as missing during the reconciliation process.

public static boolean isDiskManaged(DiskState diskState)
{
  return (DiskService.DiskOrigin.DEPLOYED == diskState.origin &&
          DiskService.DiskType.HDD == diskState.type);
}

This incorrect filtering leads to onboarded disk records being excluded from management and reconciliation activities.

Resolution

This issue has been resolved in Aria Automation version 8.18.1 Patch 2.

• The filtering logic in the reconciliation process has been updated to correctly handle disks with the ONBOARDED origin.

• Customers experiencing this issue should upgrade to 8.18.1 Patch 2 to receive the fix.

For existing environments, it's also recommended to:

1. Use the /deployment/api/deployments/{deploymentId}/resources API to collect data on both deployed and onboarded VMs.

2. Compare the records to identify any discrepancies.

3. Reconcile and validate the disk records after applying the patch.