vim.vm.device.VirtualDisk.vDiskId is always null
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm trying to use the new vSphere 6.5 vStorageObjectManager and it requires a vDiskId. Per the documentation (https://vdc-download.vmware.com/vmwb-repository/dcr-public/6b586ed2-655c-49d9-9029-bc416323cb22/fa0b429a-a695-4c11-b7d2-2cbc284049dc/doc/vim.vm.device.VirtualDisk.html) it should be returned by the vDiskId property of a vim.vm.device.VirtualDisk, however that porperty is always null for me.
Is this a bug in vCenter or in pyvmomi. Perhaps there is some compatibility flag one needs to switch on?
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 issue #652 and the linked VirtualDisk documentation, then reproduce the vSphere 6.5 case involving vStorageObjectManager and the VirtualDisk.vDiskId property. Compare the value returned by vCenter with pyvmomi's exposed property; done means identifying whether the null value is caused by pyvmomi, vCenter, or a required compatibility setting.
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