From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH-SERIES qemu-server] improve error detection/messages for some block jobs
Date: Thu, 11 Apr 2024 13:17:25 +0200 [thread overview]
Message-ID: <a5273106-8859-4759-886c-cdda67730e2a@proxmox.com> (raw)
In-Reply-To: <20240312115922.101416-1-f.ebner@proxmox.com>
Am 12.03.24 um 12:59 schrieb Fiona Ebner:
> When auto-dismiss=true (the default), a failed job can disappear very
> quickly from the job list and there might not be any chance to see the
> error in the result of 'query-block-jobs'. For jobs with $completion
> being 'auto', like 'block-stream', it couldn't even be detected that
> the job failed.
>
> Jobs with auto-dismiss=false on the other hand, will wait in
> 'concluded' state until manually dismissed. For those, it will be
> possible to query the error if the job failed.
>
> This series makes 'drive-mirror' and 'block-stream' jobs do just that.
>
> There doesn't seem to be a way to have only failed jobs stay around,
> e.g. something like auto-dismiss=on-success.
>
Superseded by a v2 also covering the new live-import:
https://lists.proxmox.com/pipermail/pve-devel/2024-April/062845.html
prev parent reply other threads:[~2024-04-11 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 11:59 Fiona Ebner
2024-03-12 11:59 ` [pve-devel] [PATCH qemu-server 1/3] blockjob: anticipate jobs with auto-dismiss=false for better error messages and detection Fiona Ebner
2024-03-12 11:59 ` [pve-devel] [PATCH qemu-server 2/3] mirror: do not auto-dismiss to allow getting error message from job Fiona Ebner
2024-03-12 11:59 ` [pve-devel] [PATCH qemu-server 3/3] live restore: do not auto-dismiss stream job to improve error message and detection Fiona Ebner
2024-04-11 11:17 ` Fiona Ebner [this message]
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=a5273106-8859-4759-886c-cdda67730e2a@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