How to set disk capacity with latest 0.9.0 release ?

[almorel]

I try to set a disk size from the libvirt_volume (Resource) with the following snippet:

resource "libvirt_volume" "ubuntu_base" {
  name   = "ubuntu-24.04-minimal-cloudimg-amd64.img"
  pool   = "guest_images_lvm"
  format = "qcow2"

  create = {
    content = {
      url = "https://cloud-images.ubuntu.com/releases/22.04/release/ubuntu-22.04-server-cloudimg-amd64.img"
    }
  }
}
...
resource "libvirt_volume" "vm_disk" {
  for_each = { for inst in var.instance_object : inst.name => inst }

  name     = "${each.value.name}-disk.qcow2"
  pool     = "guest_images_lvm"
  capacity = 10737418240
  format   = "qcow2"

  backing_store = {
    path   = libvirt_volume.ubuntu_base.path
    format = "qcow2"
  }
}

After running the code, here is what I get:

Error: Provider produced inconsistent result after apply

When applying changes to libvirt_volume.vm_disk["vm1"], provider "provider[\"registry.opentofu.org/dmacvicar/libvirt\"]" produced an unexpected new value: .backing_store.format: was
cty.StringVal("qcow2"), but now null.

This is a bug in the provider, which should be reported in the provider's own issue tracker.


Error: Provider produced inconsistent result after apply

When applying changes to libvirt_volume.vm_disk["vm1"], provider "provider[\"registry.opentofu.org/dmacvicar/libvirt\"]" produced an unexpected new value: .capacity: was
cty.NumberIntVal(1.073741824e+10), but now cty.NumberIntVal(6.9206016e+08).

This is a bug in the provider, which should be reported in the provider's own issue tracker.

It seems that the resizing of the vm1-disk.qcow2 doesn't work.

I have tried looking for config or ressources but nothing conclusive. Any help or advice ?

[kristvanbesien]

I am encountering the same issue, but not with a resize, I get it upon first creation...

╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to libvirt_volume.openwrt, provider "provider[\"registry.terraform.io/dmacvicar/libvirt\"]" produced an unexpected new value: .capacity: was cty.NumberIntVal(500), but now cty.NumberIntVal(1.3225009610752e+14).
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

The volume I am trying to create is:

resource "libvirt_volume" "openwrt" {
  name = "openwrt.img"
  pool = libvirt_pool.router.name
  capacity = 500
  capacity_unit = "MiB"
  create = {
    content = {
      url = "file://openwrt-24.10.5-x86-64-generic-ext4-combined-efi.img"
    }
  }
  target = {
    format = {
      type = "raw"
    }
  }
}

In this case the source image is smaller, and what I wish to do. here is create a raw disk of 500M, and copy the img in to it (to later resize...)

[weristdominik]

I used the following configuration with provider version `v0.9.2

resource "libvirt_volume" "vm_disk" {
  name = "test01.qcow2"
  pool = libvirt_pool.volumetmp.name

  capacity = 20 * 1024 * 1024 * 1024  # 20GB

  target = {
    format = {
      type = "qcow2"
    }
  }

  backing_store = {
    path = libvirt_volume.base.path
  }
}

Maybe this is what you are looking for.