Fix disk creation resulting in 'invalid configuration for device' error #2009
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Under some circumstances, disk creation fails with an
invalid configuration for device
error.Once this error shows up for a VM, it persistently happens whenever trying to add disks, however, I do not know how to make it show up for a VM, sometimes it is just there.
In comparing the API calls done by VCenter (which works) and ansible (which fails with the error above), I noticed that VCenter sets
fileOperation
tocreate
. Setting this in ansible, as done in this patch, fixes the disk creation in ansible.The docs describe the
fileOperation
parameter like this:So it really must be set when the backing file does not exist, (which it ofc doesn't when creating a disk).
ISSUE TYPE
COMPONENT NAME
vm_device_helper