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
Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
Terraform v1.9.6
on linux_amd64
+ provider registry.terraform.io/vmware/vcd v3.11.0
A provider update from 3.11.0 to 3.12.1 should not forces replacement of vcd_vm or vcd_vapp_vm.
Actual Behavior
After update of the provider AND you try to change a value of the vcd_vm (e.g. increase the number of cpus), this forces a replacement of the VM.
# vcd_vm.instance must be replaced
-/+ resource "vcd_vm" "instance" {
+ consolidate_disks_on_create = false # forces replacement
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Start with above HCL. Put the code above in a file main.tf
terraform init
terraform apply
Bump provider version in main.tf, e.g. sed -i s/3.11.0/3.12.1/g main.tf
terraform init -upgrade
Check: terraform -v
Terraform v1.9.6
on linux_amd64
+ provider registry.terraform.io/vmware/vcd v3.12.1
Increase cpus. E.g. sed -i s/"cpus = 2"/"cpus = 3"/g main.tf
terraform apply
You will see the replacement
vcd_vm.instance: Refreshing state... [id=urn:vcloud:vm:b1762165-5d94-4b26-9536-5bb0fa7da624]
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# vcd_vm.instance must be replaced
-/+ resource "vcd_vm" "instance" {
+ consolidate_disks_on_create = false # forces replacement
+ cpu_limit = (known after apply)
...
Important Factoids
VCD Version 10.6.0.1
The text was updated successfully, but these errors were encountered:
jpbuecken
changed the title
Upgrade path from 3.11.0 or below to 3.12 or above not smooth due force replacement by consolidate_disks_on_create
Upgrade path from 3.11.0 or below to 3.12 or above not smooth due to force replacement by consolidate_disks_on_create
Sep 19, 2024
Terraform Version
Run
terraform -v
to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Expected Behavior
A provider update from 3.11.0 to 3.12.1 should not forces replacement of vcd_vm or vcd_vapp_vm.
Actual Behavior
After update of the provider AND you try to change a value of the vcd_vm (e.g. increase the number of cpus), this forces a replacement of the VM.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform init
terraform apply
sed -i s/3.11.0/3.12.1/g main.tf
terraform init -upgrade
terraform -v
sed -i s/"cpus = 2"/"cpus = 3"/g main.tf
You will see the replacement
Important Factoids
VCD Version 10.6.0.1
The text was updated successfully, but these errors were encountered: