pvesh get /nodes/{node}/storage/{storage}/content/{volume} returns error

[sudomaster.ljs]

Hi All,

I am able to pull the contents list using the API pvesh get nodes/hv02/storage/vmstore1/content/
But call to get attributes for a specific volumes failed with below error.

root@hv02:~# pvesh get nodes/hv02/storage/vmstore1/content/ | grep vm-111-disk-0
│ raw │ 6.20 GiB │ vmstore1:vm-111-disk-0 │ │ │ │ │ │ │ │ 111 │
root@hv02:~#
root@hv02:~#
root@hv02:~# pvesh get nodes/hv02/storage/vmstore1/content/vmstore1:vm-111-disk-0
volume_size_info on 'vmstore1:vm-111-disk-0' failed
root@hv02:~#

Am i doing something wrong?

 

[Chris]

Hi All,

I am able to pull the contents list using the API pvesh get nodes/hv02/storage/vmstore1/content/
But call to get attributes for a specific volumes failed with below error.

root@hv02:~# pvesh get nodes/hv02/storage/vmstore1/content/ | grep vm-111-disk-0
│ raw │ 6.20 GiB │ vmstore1:vm-111-disk-0 │ │ │ │ │ │ │ │ 111 │
root@hv02:~#
root@hv02:~#
root@hv02:~# pvesh get nodes/hv02/storage/vmstore1/content/vmstore1:vm-111-disk-0
volume_size_info on 'vmstore1:vm-111-disk-0' failed
root@hv02:~#

Am i doing something wrong?

Hi,

what type of storage is vmstore1? The api call seems okay to me.

 

[sudomaster.ljs]

Thank you for the response. The storage type is RBD.

 

[Chris]

Thank you for the response. The storage type is RBD.

Thank you for reporting this issue, there was a bug in handling the api call. I send a patch to the mailing list, fixing this issue https://lists.proxmox.com/pipermail/pve-devel/2023-March/056016.html

 

[sudomaster.ljs]

Thanks for fixing it quickly. How can I get this patch to my already deployed proxmox (7.3-6) hosts?

 

[Chris]

Thanks for fixing it quickly. How can I get this patch to my already deployed proxmox (7.3-6) hosts?

The patch is available on the public mailing list, so if you are willing to build the package yourself and test it, you can apply it to the pve-storage repository https://git.proxmox.com/?p=pve-storage.git;a=summary

Otherwise you will have to wait for the review process and if the fix gets applied for the next package release.