public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 10/19] vzdump: list guests as skipped if the job could not start
Date: Sun,  1 Nov 2026 23:58:37 +0100	[thread overview]
Message-ID: <20261101225849.884587-11-t.lamprecht@proxmox.com> (raw)
In-Reply-To: <20261101225849.884587-1-t.lamprecht@proxmox.com>

If a job could not get the global lock, or its setup failed, for
example because the job-init hook failed or the backup server was not
reachable, none of its guests got backed up, but the notification did
not list any of them.

List them as skipped with the reason, so notifications, including those
sent only on failure, show what is missing.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
---
 PVE/API2/VZDump.pm |  3 ++-
 PVE/VZDump.pm      | 48 +++++++++++++++++++++++++++++++++++++---------
 2 files changed, 41 insertions(+), 10 deletions(-)

diff --git a/PVE/API2/VZDump.pm b/PVE/API2/VZDump.pm
index 083b9ea35..73291189f 100644
--- a/PVE/API2/VZDump.pm
+++ b/PVE/API2/VZDump.pm
@@ -143,7 +143,8 @@ __PACKAGE__->register_method({
             };
             if (my $err = $@) {
                 chomp($err); # otherwise reported as multiple problems
-                $vzdump->send_notification([], 0, $err);
+                my $tasklist = $vzdump->skip_all_guests($rpcenv, $user, 'job did not start');
+                $vzdump->send_notification($tasklist, 0, $err);
                 die "$err\n";
             }
 
diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm
index a86be4f09..b12281790 100644
--- a/PVE/VZDump.pm
+++ b/PVE/VZDump.pm
@@ -387,7 +387,10 @@ my sub format_backup_task_logs {
 
     for my $task (@$task_list) {
         my $vmid = $task->{vmid};
-        if (!$task->{tmplog}) {
+        if ($task->{state} eq 'skipped') {
+            $task_logs .= "$vmid: skipped - $task->{msg}\n\n";
+            next;
+        } elsif (!$task->{tmplog}) {
             $task_logs .= "$vmid: no log available\n\n";
             next;
         }
@@ -1400,18 +1403,11 @@ sub exec_backup_task {
     die $err if $err && $err =~ m/^interrupted by signal$/;
 }
 
-sub exec_backup {
+sub get_tasklist {
     my ($self, $rpcenv, $authuser) = @_;
 
     my $opts = $self->{opts};
 
-    debugmsg('info', "starting new backup job: $self->{cmdline}", undef, 1);
-
-    if (scalar(@{ $self->{skiplist} })) {
-        my $skip_string = join(', ', sort { $a <=> $b } @{ $self->{skiplist} });
-        debugmsg('info', "skip external VMs: $skip_string");
-    }
-
     my $tasklist = [];
     my $vzdump_plugins = {};
     foreach my $plugin (@{ $self->{plugins} }) {
@@ -1438,6 +1434,40 @@ sub exec_backup {
             };
     }
 
+    return $tasklist;
+}
+
+my sub skip_task {
+    my ($task, $reason) = @_;
+
+    $task->{state} = 'skipped';
+    $task->{msg} = $reason;
+    debugmsg('err', "Backup of VM $task->{vmid} skipped - $reason");
+}
+
+sub skip_all_guests {
+    my ($self, $rpcenv, $authuser, $reason) = @_;
+
+    my $tasklist = $self->get_tasklist($rpcenv, $authuser);
+    skip_task($_, $reason) for $tasklist->@*;
+
+    return $tasklist;
+}
+
+sub exec_backup {
+    my ($self, $rpcenv, $authuser) = @_;
+
+    my $opts = $self->{opts};
+
+    debugmsg('info', "starting new backup job: $self->{cmdline}", undef, 1);
+
+    if (scalar(@{ $self->{skiplist} })) {
+        my $skip_string = join(', ', sort { $a <=> $b } @{ $self->{skiplist} });
+        debugmsg('info', "skip external VMs: $skip_string");
+    }
+
+    my $tasklist = $self->get_tasklist($rpcenv, $authuser);
+
     # Use in-memory files for the outer hook logs to pass them to sendmail.
     my $job_start_log = '';
     my $job_end_log = '';
-- 
2.47.3





  parent reply	other threads:[~2026-11-01 23:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01 22:58 [PATCH cluster,storage,guest-common,container,manager,docs 00/19] parallel guest backups and backup concurrency limits Thomas Lamprecht
2026-11-01 22:58 ` [PATCH cluster 01/19] datacenter config: add backup concurrency setting Thomas Lamprecht
2026-11-01 22:58 ` [PATCH cluster 02/19] datacenter config: backup concurrency: add cluster-wide limit Thomas Lamprecht
2026-11-01 22:58 ` [PATCH storage 03/19] add backup concurrency option to storages Thomas Lamprecht
2026-11-01 22:58 ` [PATCH guest-common 04/19] vzdump: add options for parallel guest backups and overlapping jobs Thomas Lamprecht
2026-11-01 22:58 ` [PATCH container 05/19] vzdump: honor bandwidth limit for backups to Proxmox Backup Server Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 06/19] vzdump: notification: capture guest logs right after each backup Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 07/19] vzdump: stop all running backup jobs of the node Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 08/19] vzdump: show the error if a job could not get the global lock Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 09/19] vzdump: run job-init hook and set up target once the job may start Thomas Lamprecht
2026-11-01 22:58 ` Thomas Lamprecht [this message]
2026-11-01 22:58 ` [PATCH manager 11/19] vzdump: back up guests of a job in parallel Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 12/19] vzdump: allow jobs to run alongside each other Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 13/19] ui: options: add backup concurrency for datacenter and nodes Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 14/19] ui: backup job: add concurrency and overlap options Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 15/19] vzdump: limit concurrent guest backups cluster-wide Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 16/19] vzdump: honor backup concurrency limits of storages Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 17/19] api: backup info: add endpoints for cluster-wide backup slots Thomas Lamprecht
2026-11-01 22:58 ` [PATCH manager 18/19] ui: add cluster-wide and storage backup concurrency limits Thomas Lamprecht
2026-11-01 22:58 ` [PATCH docs 19/19] vzdump: document concurrent backups and their limits 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=20261101225849.884587-11-t.lamprecht@proxmox.com \
    --to=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal