UpdateVolume (hot)

[outscale-toa]

Description

Comportement actuel: l'action update (sur la size / iops) des volumes dans terraform n'est pas implémenté.

Le comportement est donc une re-récréation:

-     un-attach (si besoin)
-     suppression de l'ancien volume
-     creation du nouveau volume
-     attachement (si besoin)


Quand on pourra update à chaud, on pourra donc l'implémenter et sans dépendance au state de la vm.

[chrnin]

Bonjour, est-ce que l'implémentation de cette feature est à l'ordre du jour ?

[outscale-toa]

Bonjour @chrnin,
Oui, elle est en cours de développement par notre équipe API.
Merci,

[nschmerber-doca]

Hello !

Just a little adding to the problem, it happens too when you umount / dis-attach the volume.
Or even worth , no need of a VM.

terraform version : 1.11

With a VM

Sequence :

1. create a VM with TF
2. create a volume and a volume link resource to see it in the VM
3. format / mount / put test files in the VM
4. umount the volume
5. remove the outscale_volume_link resource (not the volume)
6. At this point the VM doesnt see anymore the disk
7. try to change the size of the volume resource
8. Terraform plans to destroy the volume to create a new one ..

Even with no VM

In fact you can just try just this :

resource "outscale_volume" "vol" {
subregion_name = "cloudgouv-eu-west-1b"
size = 20
volume_type = "standard"
}

• terraform apply -> OK
• change the size :

resource "outscale_volume" "vol" {
subregion_name = "cloudgouv-eu-west-1b"
size = 20
volume_type = "standard" #it also fails with "gp2"
}

  # outscale_volume.vol must be replaced
-/+ resource "outscale_volume" "vol" {
      ~ creation_date  = "2025-05-16T20:56:23.300Z" -> (known after apply)
      ~ id             = "vol-a3560964" -> (known after apply)
      ~ iops           = 150 -> (known after apply)
      ~ linked_volumes = [] -> (known after apply)
      + request_id     = (known after apply)
      ~ size           = 10 -> 20 # forces replacement
      + snapshot_id    = (known after apply)
      ~ state          = "available" -> (known after apply)
      ~ volume_id      = "vol-a3560964" -> (known after apply)
        # (2 unchanged attributes hidden)
    }

Thanks in advance.

Nicolas

[outscale-toa]

Hi Nicolas (@nschmerber-doca)

Actually update volume or block device mapping (size/iops/volume_type) is not implemented in terraform provider yet.

• In your workaround, you have to update the volume size size = 20 in your terraform state file (terraform.tfstate ) before running terraform refresh or terrafrom apply

• There is a workaround for block device mapping and it is the same with volume. Terraform want to rebuild VM if I want to increase disk size #310 (comment)

Best regards,