Cloning a template while deleting several machines throws ManagedObjectNotFound
Open
Nobody has claimed this yet.
needs verification
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
This occurs every so often in my codebase, sometimes when deleting a few machines at once, and then cloning a machine(simultaneously), this exception is thrown and the machine is not cloned.
pyVmomi.VmomiSupport.ManagedObjectNotFound: (vmodl.fault.ManagedObjectNotFound) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = "The object 'vim.VirtualMachine:vm-58107' has already been deleted or has not been completely created",
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
obj = 'vim.VirtualMachine:vm-58107'
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository file, test, or entry point. Start by locating the machine-deletion and machine-cloning paths, then investigate the concurrent operation described and the ManagedObjectNotFound exception; done means the reported concurrent scenario no longer prevents cloning and is covered by a reproducible test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100