https://ovirt.mydomains/ovirt-engine/apidoc/#/ is not working (page is blank, has ovirt horizontal menu, but content is empty). You may mean the page https://ovirt.mydomains/ovirt-engine/apidoc/#/services/disk/methods/update It works for me, but the information I see on it seems insufficient (unusable) to me: update This operation updates the disk with the appropriate parameters. The only field that can be updated is qcow_version. For example, disk update can be done using the following request: PUT /ovirt-engine/api/disks/123 With a request body like this: <disk> <qcow_version>qcow2_v3</qcow_version> </disk> Since the backend operation is asynchronous, the disk element that is returned to the user might not be synced with the changed properties. I have HTTP Error 400: Bad Request Request syntactically incorrect. But syntax is OK: Ansible: --- - name: REST call w XML body uri: url: https://ovirt.{{ domain }}/ovirt-engine/api/disks/{{ diskid }} user: {{ user }} password: {{ password }} method: PUT validate_certs: no headers: Content-Type: "application/xml" #body_format: raw body: "{{lookup('file','put.xml')}}" register: result put.xml: <disk> <provisioned_size>18737418240</provisioned_size> </disk>

On Tuesday, 5 October 2021 09:47:45 CEST ovirt.org(a)nevim.eu wrote: which says "The only field that can be updated is qcow_version." I guess you are looking for disk_attachment update, in this manual here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/...

On Tuesday, 5 October 2021 15:44:40 CEST ovirt.org(a)nevim.eu wrote: <active>true</active> <vm <provisioned_size> should do the job, try to use XML snippet from https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/...

Hi, The ability to update a disk and its size was upgraded in 4.4 http://ovirt.github.io/ovirt-engine-api-model/4.4/#services/disk/methods/... That way, you can edit floating disk parameters, such as extend its size, without attaching the disk to a VM. On version 4.3, as already mentioned, the disk should be attached to the VM. In your case, you can see the disk's size with the following request: GET https://ovirt.domain.com/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a... Is there some more info on the engine log? *Regards,* *Shani Leviim* On Tue, Oct 5, 2021 at 10:05 PM <ovirt.org(a)nevim.eu&gt; wrote:

On Wednesday, 6 October 2021 15:14:10 CEST ovirt.org(a)nevim.eu wrote: .... <disk> It does, but the disk has t be attached to a VM (Vm don't has to be running). Example XML (extend.xml): <disk_attachment> <disk> <provisioned_size>2147483648</provisioned_size> </disk> </disk_attachment> Example command using this XML: curl --insecure -X PUT --header "Accept: application/xml" --header "Content-Type: application/xml" --user "admin@internal:ovirt" -T extend.xml https://engine-test.local/ovirt-engine/api/vms/651faf06-9dd3-41a5-94f6-ef...

Glad it worked :) I'll try to fill the gap, so maybe things will make more sense. The API you dealt with has 2 basic services - Disk <http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/disk> and Disk_Attachment <http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/disk_attachme... . In 4.3, once you're interested in a disk attached to a VM, the service you need to use is *disk_attachment*. (So the GET, PUT POST refers to the disk_attachment service). Basically, in order to edit a disk (any disk), you need to attach it to a VM (any VM), and only then update its parameters (name, interface, size, etc). Even if you want to edit a floating disk (a disk you've just created and wants to change its name for instance), you need to attach it to a VM, edit its name and then detach it from the VM back, so it will be floating again. In 4.4, we've changed that behavior, so editing disks will be available also for floating disks https://www.ovirt.org/develop/release-management/features/storage/editing... That means that you can edit the disk "as disk", not necessarily attached to a VM, and use the *disk* service. So in your case, the service you need to use in order to update is disk_attachment. Now, regarding the provisioned_size field, on your GET request, you've received the following response: <disk_attachment href="/ovirt-engine/api/vms/678faf6f-fa5f-4785-a365-e1b85925575f/diskattachments/f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc" id="f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc"> <active>true</active> <bootable>true</bootable> <interface>virtio_scsi</interface> <pass_discard>false</pass_discard> <read_only>false</read_only> <uses_scsi_reservation>false</uses_scsi_reservation> *<disk href="/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc" id="f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc"/>* <vm href="/ovirt-engine/api/vms/678faf6f-fa5f-4785-a365-e1b85925575f" id="678faf6f-fa5f-4785-a365-e1b85925575f"/> </disk_attachment> This means that the disk_attachment, the disk that attached to your VM, also has a reference to the disk itself "as a disk". By sending a GET request for */ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc*, you'll get a response of the following form: <disk href="/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc" id="f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc"> <actions> ... </actions> <name>your-disk-name</name> <description></description> <vms> <vm href="/ovirt-engine/api/vms/678faf6f-fa5f-4785-a365-e1b85925575f" id="678faf6f-fa5f-4785-a365-e1b85925575f"/> </vms> <provisioned_size>2147483648</provisioned_size> <shareable>false</shareable> <status>ok</status> <storage_domains> ... </storage_domains> </disk> Here, you can see the disk's parameters. So actually, by sending an update request of the form: <disk_attachment> <disk> <provisioned_size>2147483648</provisioned_size> </disk> </disk_attachment> Means something like "go to the disk attachment of my VM, and update the disk elements with the following fields and values". Hope it makes more sense. *Regards,* *Shani Leviim* On Thu, Oct 7, 2021 at 9:27 AM <ovirt.org(a)nevim.eu&gt; wrote: