-
Notifications
You must be signed in to change notification settings - Fork 449
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
vsphere_virtual_disk created on v2.6.1 errors when running terraform plan with v2.7.0 #2162
Comments
Hello, Jusaa! 🖐 Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle. If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests. |
Same for me: Terraform Terraform Provider VMware vSphere When changed vsphere provider version to 2.2.0 or even 2.6.1 it worked |
We've picked up govmomi 0.37.1 |
Can confirm it works, we successfully updated to v2.8.1 without any problems! |
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Community Guidelines
Terraform
v1.6.6
Terraform Provider
v2.7.0
VMware vSphere
v7.0.3.01700
Description
Upgrading to terraform-provider-vsphere v2.7.0 introduced a breaking bug for vsphere_virtual_disks created with older versions.
This happens as the vmdk_path variable is now correctly set after this fix: #1762
I tried changing the vmdk_path to match the actual old value from vsphere but it doesn't work, and it shouldn't work if I understand the code change correctly. What would be the proper steps to be able to upgrade to latest provider version?
Affected Resources or Data Sources
resource/vsphere_virtual_disk
Terraform Configuration
Debug Output
Planning failed. Terraform encountered an error while generating this plan.
│ Error: Failed to query disk type
│
│ with module.example-data.vsphere_virtual_disk.main,
│ on ../../modules/disk/main.tf line 5, in resource "vsphere_virtual_disk" "main":
│ 5: resource "vsphere_virtual_disk" "main" {
│
Panic Output
No response
Expected Behavior
Plan after update to provider v2.7.0 passes with either no changes or possible change to the vsphere_virtual_disk configuration
Actual Behavior
Plan after update to provider v2.7.0 errors out
Steps to Reproduce
Environment Details
No response
Screenshots
No response
References
No response
The text was updated successfully, but these errors were encountered: