-
Notifications
You must be signed in to change notification settings - Fork 454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing cloning regression on DS cluster #2037
Fixing cloning regression on DS cluster #2037
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Issue is that when vm is cloned on DS cluster the datastore_id field in the relocate spec holds invalid value which causes the vCenter to throw an error. The fix was to restore previously implemented behavior to not send relocate specs for the VM hard disks when it is cloned on DS Cluster with exception when datastore_id is explicitly specified for the Hard Disk. Added TestAccResourceVSphereVirtualMachine_cloneOnDsCuster to cover the case. Fixes hashicorp#2034 Signed-off-by: Vasil Atanasov <[email protected]>
4dc8f18
to
e208779
Compare
Removed disk with separate DS from the e2e , currently conflicting with
This is not exactly correct behaviour, since the UI supports cloning a VM with 1 disk on the DS cluster and another on a separate DS |
This functionality has been released in v2.5.1 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Issue is that when vm is cloned on DS cluster the datastore_id field in the relocate spec holds invalid value which causes the vCenter to throw an error. The fix was to restore previously implemented behaviour to not send relocate specs for the VM hard disks when it is cloned on DS Cluster with exception when datastore_id is explicitly specified for the Hard Disk.
Added TestAccResourceVSphereVirtualMachine_cloneOnDsCuster to cover the case.
Fixes #2034
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
#2034