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
set up a VM "test_vm" with a disk "disk_of_test_vm" from terraform; this disk will have "initial_uuid"
create a new disk "disk_of_test_vm" in the Web UI (for example as the result of a recovered snapshot), with "new_uuid"
poweroff the VM in the Web UI
unmount the currently mounted "disk_of_test_vm" and mount/attach the newly created "disk_of_test_vm" to it
start the VM in the Web UI
do a terraform plan
In earlier times, in this situation terraform would have reported a change, afair, but it anyways should detect that difference between the local state and the remote situation.
But it says, that everything is in sync.
If we look into the terraform.tfstate json file, we can see, that:
the "disk_of_test_vm" with "initial_uuid" is still present, but its state automatically has been changed to "unmounted"
the "test_vm" has a "drive" that still is "initial_uuid" .
We even have written a shell script, that supports us, replacing the "initial_uuid" with the "new_uuid" in situations like the described one in the past;
but if we are not warned about the difference, strange things will happen: for example the attempt to increase the disk from terraform would increase the old, unmounted disk, if it still is present.
And what would terraform plan report, if we would delete the drive with "initial_uuid" ? How would the next plan change the local state ?
Terraform Version
Terraform v1.1.9
on windows_amd64
+ provider registry.terraform.io/cloudsigma/cloudsigma v1.10.1
Affected Resource(s)
cloudsigma_server
cloudsigma_drive
Expected Behavior
terraform plan should notice the difference between local state and remote situation
Actual Behavior
No difference is detected.
Steps to Reproduce
See in Description
!--- Please keep this note for the community --->
Community Note
Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Bug report
Description
terraform plan
In earlier times, in this situation terraform would have reported a change, afair, but it anyways should detect that difference between the local state and the remote situation.
But it says, that everything is in sync.
If we look into the terraform.tfstate json file, we can see, that:
We even have written a shell script, that supports us, replacing the "initial_uuid" with the "new_uuid" in situations like the described one in the past;
but if we are not warned about the difference, strange things will happen: for example the attempt to increase the disk from terraform would increase the old, unmounted disk, if it still is present.
And what would
terraform plan
report, if we would delete the drive with "initial_uuid" ? How would the nextplan
change the local state ?Terraform Version
Affected Resource(s)
Expected Behavior
terraform plan
should notice the difference between local state and remote situationActual Behavior
No difference is detected.
Steps to Reproduce
See in Description
!--- Please keep this note for the community --->
Community Note
to the original issue to help the community and maintainers prioritize this request
The text was updated successfully, but these errors were encountered: