You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vote on this issue by adding a 馃憤 reaction to the original issue initial description to help the maintainers prioritize.
Do not leave "+1" or other comments that do not add relevant information or questions.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Terraform
1.6.6
Terraform Provider
2.6.1
VMware vSphere
7.0.3
Description
When creating a VM from template via clone in terraform and using a datastore_cluster as the destination storage the disk provisioning settings are not correctly applied.
#2028 appears to have mostly fixed the problem for datastores(see my other issue) but the problem is still present when using a datastore cluster destination.
I have tested the following:
thin-template -> Request eager zero configured VM disk -> results in thin VM disk (Fail)
thin-template -> Request lazy zero configured VM disk -> results in thin VM disk (Fail)
thin-template -> Request thin configured VM disk -> results in thin VM disk (Pass)
lazy-zero-template -> Request eager zero configured VM disk -> results in lazy-zero VM disk (Fail)
lazy-zero-template -> Request lazy zero configured VM disk -> results in lazy-zero VM disk (Pass)
lazy-zero-template -> Request thin configured VM disk -> results in lazy-zero VM disk (Fail)
The Pass in my tests are a result of the source and destination settings matching. When attempting to use different disk settings than the source template they will not apply correctly.
Community Guidelines
Terraform
1.6.6
Terraform Provider
2.6.1
VMware vSphere
7.0.3
Description
When creating a VM from template via clone in terraform and using a datastore_cluster as the destination storage the disk provisioning settings are not correctly applied.
#2028 appears to have mostly fixed the problem for datastores(see my other issue) but the problem is still present when using a datastore cluster destination.
I have tested the following:
thin-template -> Request eager zero configured VM disk -> results in thin VM disk (Fail)
thin-template -> Request lazy zero configured VM disk -> results in thin VM disk (Fail)
thin-template -> Request thin configured VM disk -> results in thin VM disk (Pass)
lazy-zero-template -> Request eager zero configured VM disk -> results in lazy-zero VM disk (Fail)
lazy-zero-template -> Request lazy zero configured VM disk -> results in lazy-zero VM disk (Pass)
lazy-zero-template -> Request thin configured VM disk -> results in lazy-zero VM disk (Fail)
The Pass in my tests are a result of the source and destination settings matching. When attempting to use different disk settings than the source template they will not apply correctly.
Affected Resources or Data Sources
'resource/vsphere_virtual_machine'
Terraform Configuration
https://gist.github.com/TrevGG/a9e1c483d886fd65fa634602b313f29f
Debug Output
N/A
Panic Output
No response
Expected Behavior
Requested disk configuration should be applied.
Actual Behavior
Disk configuration is not applied (unless the same as source).
Steps to Reproduce
Create VM from template with disk settings that differ from source template.
Environment Details
No response
Screenshots
No response
References
No response
The text was updated successfully, but these errors were encountered: