From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied-series: [PATCH proxmox-backup 0/2] schedule prunes even with keep-all
Date: Tue, 14 Jul 2026 12:53:31 +0200 [thread overview]
Message-ID: <178402620783.364806.5570849530271223914.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260608085919.288332-1-c.ebner@proxmox.com>
On Mon, 08 Jun 2026 10:59:17 +0200, Christian Ebner wrote:
> Currently prune jobs without keep options will keep all snapshots, but
> they are actually never scheduled. This caused a report in the
> enterprise support about an unexpectedly `pending` job state, manual
> execution of the job running just fine.
>
> Drop the early check for no keep options being set and actually run
> the task on schedule, as this might also be used for testing only.
> Further, escalate the info message for keep-all in case of no prune
> options being set to a warning, so users can more easily identify
> such jobs, but without breaking current behaviour with respect to
> notifications.
>
> [...]
Applied, thanks!
[1/2] proxy: scheduler: drop early return for keep-all prune jobs
commit: 28a6dd3327f0469bf46c3e9ea1b89f83668aa28a
[2/2] prune job: escalate keep-all from info to warning
commit: a36f0674f778fee992bf19ee16e213d40f51a026
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-07-14 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 8:59 [PATCH proxmox-backup 0/2] schedule prunes even with keep-all Christian Ebner
2026-06-08 8:59 ` [PATCH proxmox-backup 1/2] proxy: scheduler: drop early return for keep-all prune jobs Christian Ebner
2026-06-08 8:59 ` [PATCH proxmox-backup 2/2] prune job: escalate keep-all from info to warning Christian Ebner
2026-07-14 10:53 ` Fabian Grünbichler [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=178402620783.364806.5570849530271223914.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-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