This seems to be a recurring issue for others as well, but the root cause might be different for each
I am in a situation where I can't add additional disks to a VM because of running intoError (2602) "Unable to perform the job because one or more of the selected objects are locked by another job" - however, other VMs on the cluster are not locked and there are no other jobs running against the VM where I need to add the disks.
Looks like a quirk in the VMM database to me - maybe an "orphaned lock"? Would love to know how to remove this or how to handle this issue, as the recommended action in VMM doesn't really help much at all (To find out which job is locking the object, in the Jobs view, group by Status, and find the running or canceling job for the object. When the job is complete, try again.)
Why doesn't VMM at least say which job is locking the object?