Open mars4life opened 3 months ago
Hello Amakou,
This is a know issue of the provider since we cannot create disks at the virtual machine level. What's happening here is that when vSphere receives two (or more) requests to create a virtual disk simultaneously, it processes them sequentially. But if the first disk creation has been too long, it can refuse to process the following disk creation requests considering the situation has changed between the moment it received the request and the one it is able to process it.
One solution we could implement would be to create disks at the virtual machine level (in the cloudtemple_compute_virtual_machine
resource) with a new virtual_disks
property for example.
But this solution would be very time consuming, and we cannot afford it for the moment.
In conclusion, a viable workaround, as you said would be to use the parameter parallelism=1
or to make the cloudtemple_compute_virtual_disk
dependent to the previous one.
I'll let your issue open and link it to another one that is related, since we plan to implement a long-term solution in the future.
Thanks for your understanding.
Kind regards, Paul.
Hello Paul, Thanks for your quick and precise answer. I completely understand that it takes a lot of time to implement a real clean solution. I'll see which workaround I'll implement meantime. KR, Amakou
Describe the bug An error occurs when I try to add 2 disks at the same time terraform version : 1.6.4 and also with 1.7.5 provider version : v0.13.0-rc.1
Current Behavior
An error occurs (Invalid date) when I try to add 2 disks at the same time. Only 1 disk is added if I reapply the same configuration, the second disk is then added. I think the error is because the disk are added simultaneous , but putting parallelism=1 is not a solution for me.
Expected behavior The 2 disks are added.
Steps to reproduce Steps to reproduce the behavior:
Screenshots If applicable, add screenshots to help explain your problem.
Additional context The error message: