From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES] correctly handle warnings status
Date: Wed, 12 May 2021 14:32:49 +0200 [thread overview]
Message-ID: <20210512123258.28178-1-f.ebner@proxmox.com> (raw)
There's a few places where we use the logic "OK" if and only if no error for a
task status, but this is no longer true now that we also support ending in a
warnings status (not yet used by anything, but the feature is there).
Everything depends on the first patch and depedency bumps for pve-common
are needed across the board.
pve-common:
Fabian Ebner (1):
tools: add upid_status_is_error function
src/PVE/Tools.pm | 8 ++++++++
1 file changed, 8 insertions(+)
pve-manager:
Fabian Ebner (4):
api/cli: tasks: don't treat warnings status as an error status
nodes: startall: correctly handle warning status for delayed task
cli: pveam: remove unused private sub
cli tools: correctly handle warnings status
PVE/API2/Nodes.pm | 2 +-
PVE/API2/Tasks.pm | 5 ++++-
PVE/CLI/pveam.pm | 6 ------
PVE/CLI/pveceph.pm | 2 +-
PVE/CLI/pvenode.pm | 7 +++++--
PVE/CLI/vzdump.pm | 2 +-
6 files changed, 12 insertions(+), 12 deletions(-)
pve-storage:
Fabian Ebner (1):
api: content: correctly handle warnings status for delayed task
PVE/API2/Storage/Content.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pve-container:
Fabian Ebner (1):
pct: correctly handle warnings task status
src/PVE/CLI/pct.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
qemu-server:
Fabian Ebner (2):
cli tools: correctly handle warnings task status
api: update vm: correctly handle warnings status for delayed task
PVE/API2/Qemu.pm | 2 +-
PVE/CLI/qm.pm | 2 +-
PVE/CLI/qmrestore.pm | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2021-05-12 12:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 12:32 Fabian Ebner [this message]
2021-05-12 12:32 ` [pve-devel] [PATCH common 1/9] tools: add upid_status_is_error function Fabian Ebner
2021-06-17 13:23 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH manager 2/9] api/cli: tasks: don't treat warnings status as an error status Fabian Ebner
2021-06-24 7:06 ` Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH manager 3/9] nodes: startall: correctly handle warning status for delayed task Fabian Ebner
2021-06-24 7:04 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH manager 4/9] cli: pveam: remove unused private sub Fabian Ebner
2021-06-24 7:04 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH manager 5/9] cli tools: correctly handle warnings status Fabian Ebner
2021-06-24 7:04 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH storage 6/9] api: content: correctly handle warnings status for delayed task Fabian Ebner
2021-06-23 20:22 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH container 7/9] pct: correctly handle warnings task status Fabian Ebner
2021-06-23 20:17 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH qemu-server 8/9] cli tools: " Fabian Ebner
2021-06-23 10:53 ` [pve-devel] applied: " Thomas Lamprecht
2021-05-12 12:32 ` [pve-devel] [PATCH qemu-server 9/9] api: update vm: correctly handle warnings status for delayed task Fabian Ebner
2021-06-23 10:53 ` [pve-devel] applied: " Thomas Lamprecht
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=20210512123258.28178-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox