public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox-backup 0/2] schedule prunes even with keep-all
Date: Mon,  8 Jun 2026 10:59:17 +0200	[thread overview]
Message-ID: <20260608085919.288332-1-c.ebner@proxmox.com> (raw)

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.

Christian Ebner (2):
  proxy: scheduler: drop early return for keep-all prune jobs
  prune job: escalate keep-all from info to warning

 src/bin/proxmox-backup-proxy.rs | 4 ----
 src/server/prune_job.rs         | 2 +-
 2 files changed, 1 insertion(+), 5 deletions(-)

-- 
2.47.3





             reply	other threads:[~2026-06-08  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08  8:59 Christian Ebner [this message]
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

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=20260608085919.288332-1-c.ebner@proxmox.com \
    --to=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal