Error: "Null value was assigned to a property of primitive type setter of com.vmware.vcloud.common.model.VmSnapshotViewModel.snapshotUid" when attempting to view or delete snapshots of Virtual Machine

Products

• VMware Cloud Director

Issue/Introduction

• After upgrading to Cloud Director 10.6 you cannot view or delete snapshots of Virtual Machine (VM) inside VMware Cloud Director (VCD) User Interface (UI).
• However, the snapshots can be viewed inside vCenter and looks correct.
• You receive an error message in the VCD UI when attempting to view, delete or manage snapshots:

Null value was assigned to a property of primitive type setter of com.vmware.vcloud.common.model.VmSnapshotViewModel.snapshotUid

Error: "[ ####-####-####-####-#### ] Internal Server Error - (vmodl.fault.ManagedObjectNotFound) { faultCause = null, faultMessage = null, obj =                        ManagedObjectReference: type = VirtualMachineSnapshot, value = snapshot-####, serverGuid = null } - The object 'vim.vm.Snapshot:snapshot-####' has already been deleted  or has not been completely created" when attempting to delete snapshots of Virtual Machine(VM).

• Need to delete orphaned snapshot from the database.
• "There no snapshots available for this VM" message and "Error" message are displayed on the virtual machines snapshot UI (vApps -> VM Name -> Snapshots).
• You will see a mismatch of the total space consumption between vCenter and VCD

Environment

VMware Cloud Director 10.6.0.x
VMware Cloud Director 10.6.1

Cause

VMware Cloud Director 10.6 introduced the ability to have more than 1 snapshot.

This issue occurs when snapshots exist in VMware Cloud Director's database that don't exist in vCenter Server.

Resolution

This issue has been resolved in Cloud Director 10.6.1.1 which is available to download here.

Important Notes:

• Starting with version 10.6.1, a design change was introduced in Cloud Director, where it actively synchronizes snapshot data from the underlying vCenter. As part of this enhancement, Cloud Director now calculates storage usage—including snapshots—based on information retrieved via the vCenter Snapshot API.

• As a result, storage consumed by snapshots, including those created temporarily by backup solutions, is now counted against the Org VDC’s allocated storage. This can lead to a reduction in reported available storage, even when the snapshots are short-lived or managed externally.

• While this behavior is by design in version 10.6.1, it has led to unexpected storage accounting scenarios. This behavior was further refined and addressed in version 10.6.1.1 to improve accuracy and usability.

Additional Information

A change in storage allocation logic was introduced in VMware Cloud Director 10.6.1.1 release,  refining how snapshot storage is calculated. With this update, temporary snapshots—such as those created by backup solutions—are no longer incorrectly counted against the Org VDC's allocated storage.

For more details, please refer to Broadcom KB 394637.