What is the proper way to resignature an unresolved volume?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
What is the proper way to resignature an unresolved volume so that the volume will be auto-mounted across all hosts that the volume is mapped to (the same way like resignaturing using the vsphere client)?
I'm currently using host.configManager.datastoreSystem.ResignatureUnresolvedVmfsVolume(), but when, for example, I map a volume to 2 hosts and then run this method on one of them, then at the other host the volume is still recognized as "unresolved".
At the method documentation it's written - "Users can specify a list of hosts on which the volume will be auto-mounted.", So... how do I specify this list of hosts? :)
Thanks.
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 host.configManager.datastoreSystem.ResignatureUnresolvedVmfsVolume() and its method documentation; compare it with the vSphere Client workflow and the two-host unresolved-volume scenario. Done would require documenting how to specify hosts or clarifying the API behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100