jnm27
jnm27
Usually the paradigm is, right before any actual change is made, module.check_mode is checked, at the lowest granularity for any change.
I am hitting this issue as well. Ansible 2.11, pyvmomi 7.0, vmware 6.7.
I found this at line 2681 of vmware_guest: # which datastore? if expected_disk_spec.get('datastore'): # TODO: This is already handled by the relocation spec, # but it needs to eventually be...
https://github.com/Akasurde/ansible/commit/7ad11a1f8bbf757226ed190fa0596ac76542f947 was made but never merged. Per comments in https://github.com/ansible/ansible/issues/26095, this improved the situation, in that it allows one disk per datastore. It will fail with multiple disks in a...
I just tested it and this patch does work! I will not be bringing it through process here but plan to use it informally until it is officially merged.
Is there any chance of this making it into an official build? I've been carrying around an unofficial patch for awhile now but I want to step up to the...
We found a bug in @Akasurde's patch code. The directory creation in vmware_guest.py:create_directory_for_datadisk is not necessary and it actually causes duplicate directories to be created. It creates , and then...
Follow-up to my previous "fix". It appears to be version specific. That code should not be there for ESXi 6.7, but it may need to be there for ESXi 7.0.
Yet another fix... @Akasurde when will this be worked for real? I also needed to apply a similar patch in the configure_multiple_controllers_disks function to handle the case where a new...