all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Andrei Perapiolkin via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
Subject: [pve-devel] checking output of storage plugin API - volume_rollback_is_possible(..., blockers)
Date: Wed, 14 May 2025 08:44:11 -0400	[thread overview]
Message-ID: <mailman.409.1747226995.394.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 6495 bytes --]

From: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] checking output of storage plugin API - volume_rollback_is_possible(..., blockers)
Date: Wed, 14 May 2025 08:44:11 -0400
Message-ID: <1979bee4-2f4e-4af2-bfb4-3c320f37399e@open-e.com>

Hi,

I'm trying to test specific aspects of the storage plugin API,
and I'm not sure how to verify whether my function 
volume_rollback_is_possible
correctly sets up the blockers list.

I've checked REST API documentation:
https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/qemu/{vmid}/snapshot/{snapname}/rollback

CLI tool:
qm rollback

But I couldn't find where the list of blockers is returned or printed.

Are there any posts, guides, or documentation on how to test blockers or 
other return values from storage plugins?



Best regards,

Andrei Perepiolkin



[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

             reply	other threads:[~2025-05-14 12:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 12:44 Andrei Perapiolkin via pve-devel [this message]
2025-05-15  9:16 ` Fabian Grünbichler
2025-05-15 11:23   ` Andrei Perapiolkin via pve-devel
     [not found]   ` <d32e8977-da91-427e-aa15-4937f9894fe3@open-e.com>
2025-05-15 12:28     ` Fabian Grünbichler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.409.1747226995.394.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=andrei.perepiolkin@open-e.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal