-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
0.7rc2 forces to destroy existing vsphere resources due to enable_disk_uuid #7275
Comments
I am currently bypassing this issue by manually editing the local tfstate to add |
Looks like a state migration was missed here P. |
hi @shravanpn7 Thanks for reporting the issue here. I am going to get this fixed before 0.7 hits Paul |
`virtual_machine` Fixes #7275 - a state migration was missed when `enable_disk_uuid` was merged ``` make testacc TEST=./builtin/providers/vsphere TESTARGS='-run=TestVSphereVirtualMachineMigrateState' ==> Checking that code complies with gofmt requirements... go generate $(go list ./... | grep -v /vendor/) TF_ACC=1 go test ./builtin/providers/vsphere -v -run=TestVSphereVirtualMachineMigrateState -timeout 120m === RUN TestVSphereVirtualMachineMigrateState --- PASS: TestVSphereVirtualMachineMigrateState (0.00s) PASS ok github.com/hashicorp/terraform/builtin/providers/vsphere 0.018s ```
We may have another as well. Disk controllers. |
@chrislovecnm nah, looks like disk controller_type has already been taken care of in the migration function |
Awesome!! |
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. |
Hello,
I have few vsphere_virtual_machine resources created using 0.6.16 and I switched to 0.7rc2 to test if #6590 is fixed. When i run my plan, its destroying existing resource because the 'enable_disk_uuid' is not present in 0.6.16.
Terraform Version
Terraform v0.7.0-rc2 (46a0709)
Affected Resource(s)
Terraform Configuration Files
Plan output
Panic Output
N/A
Expected Behavior
Should run and apply plan with out destroying exisitng resources which doesnt have enable_disk_uuid flag
Actual Behavior
The vsphere_virtual_machine are being destroyed if the existing resources doesnt have enable_disk_uuid flag
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
terraform apply
The text was updated successfully, but these errors were encountered: