Abnormal behavior of PyVmomi SDK when Datastore get detached
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
We have noticed when any datastore get disconnected/detached , and we have any job of vcenter of detached datastore, it gives abnormal behavior.
Many times it get stuck while creating view reference or fetching property using pyVmomi SDK.
Some times it get resumed after some time, and in some cases it stays stuck and we dont get any log messages in log files.
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
No file, test, or code entry point is identified in the issue. Start by reproducing a datastore detach while a vCenter job creates a view reference or fetches properties through the pyVmomi SDK, then determine where the operation stops and whether logging records the stall; done means the behavior is understood and the hang or missing progress is addressed.
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