schedule-analyze: fix schedules with limited runs

When a schedule only has a limited amount of runs it can happen
(e.g. 2022-10-01 8:00/30), $next will be undef after the last run.
Exit early in that case.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>

diff --git a/PVE/API2/Cluster/Jobs.pm b/PVE/API2/Cluster/Jobs.pm
index 2699442a76a17b7df37bd794b6243f2fa76008ac..8166333dcf5ea395b6bec16a33577d2cb8c082a3 100644 (file)
--- a/PVE/API2/Cluster/Jobs.pm
+++ b/PVE/API2/Cluster/Jobs.pm
@@ -97,6 +97,7 @@ __PACKAGE__->register_method({
 
        for (my $count = 0; $count < $iterations; $count++) {
            my $next = PVE::CalendarEvent::compute_next_event($event, $starttime);
+           last if !defined($next);
            push @$result, {
                timestamp => $next,
                utc => scalar(gmtime($next)),