Question about Finding a "bad VM"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I have been working with rvtools which is a app that fetches vm related information from vcenter. The way Rvtools work is that it filters out the bad vms which is nothing but a VM with hundreds of disks. The problem seems to be mainly caused by backup solutions that cannot clean everything properly when the backup is finished. I don't see this case with pyvmomi. How can i detect a "bad vm" using pyvmomi?
Reproduction steps
- Get all vm related info using retrievePropertyEX
Expected behavior
The result should filter out all the bad vms.
Additional context
No response
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
Start with the retrievePropertyEX call described in the reproduction steps and review how pyvmomi exposes VM-related information. Determine which available properties identify a VM with hundreds of disks or leftover backup resources, and document a reproducible way to filter such VMs. The issue provides no file or test name, so the relevant entry point and validation case must first be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100