From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 07B8B1FF13B for ; Mon, 08 Jun 2026 10:59:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7B31217582; Mon, 8 Jun 2026 10:59:37 +0200 (CEST) From: Christian Ebner 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 Message-ID: <20260608085919.288332-1-c.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1780909129282 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.068 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox-backup-proxy.rs] Message-ID-Hash: O5UOYIF4ATCYGDQVRGG4DXOAJH3I35GZ X-Message-ID-Hash: O5UOYIF4ATCYGDQVRGG4DXOAJH3I35GZ X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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