Null value was assigned to a property of primitive type setter of com.vmware.vcloud.common.model.VmSnapshotViewModel.snapshotUidError: "[ ####-####-####-####-#### ] 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).
"Exceeded the maximum number of permitted snapshots" VMware Cloud Director 10.6.0.x
VMware Cloud Director 10.6.1
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.
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.