The 'bootTime' parameter of RuntimeInfo at the migrated VMs is unset.
Open
Nobody has claimed this yet.
bug
needs verification
question
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
About the 'bootTime' parameter of vim.vm.RuntimeInfo which is got from vim.VirtualMachine,
some VMs doesn't have that. And each of them are migrated after the boot.
This problem is occurred on the following environment.
- ESXi: 5.5.0, build: 2068190
- vCenter: 5.5.0, build: 3252642
- pyvmomi: latest of master branch (commit: 4c9debad21bb284c61a64e7c7cb7388b9d0ce4e2)
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 by reproducing the missing vim.vm.RuntimeInfo.bootTime value for migrated VMs using the ESXi, vCenter, and pyvmomi versions listed in the issue. Investigate whether the value is absent in the vSphere response or lost in pyvmomi, and document the cause and expected handling when the behavior is understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100