From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 2/2] cli: pve8to9: check for legacy 'notification-{policy, target}' options
Date: Tue, 24 Jun 2025 13:33:27 +0200 [thread overview]
Message-ID: <20250624113327.134893-2-l.wagner@proxmox.com> (raw)
In-Reply-To: <20250624113327.134893-1-l.wagner@proxmox.com>
These were briefly used by the first version of the overhauled
notification stack which hit pvetest too soon. They will be dropped from
the schema in the major update.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
PVE/CLI/pve8to9.pm | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
diff --git a/PVE/CLI/pve8to9.pm b/PVE/CLI/pve8to9.pm
index 5a80c40f..19667619 100644
--- a/PVE/CLI/pve8to9.pm
+++ b/PVE/CLI/pve8to9.pm
@@ -17,6 +17,7 @@ use PVE::Ceph::Tools;
use PVE::Cluster;
use PVE::Corosync;
use PVE::INotify;
+use PVE::Jobs;
use PVE::JSONSchema;
use PVE::NodeConfig;
use PVE::RPCEnvironment;
@@ -1452,6 +1453,39 @@ sub check_legacy_notification_sections {
}
}
+sub check_legacy_backup_job_options {
+ log_info(
+ "Check for legacy 'notification-policy' or 'notification-target' options in /etc/pve/jobs.cfg..."
+ );
+
+ my $job_cfg = PVE::Cluster::cfs_read_file('jobs.cfg');
+
+ my $failed = 0;
+
+ for my $jobid (sort keys $job_cfg->{ids}->%*) {
+ my $cfg = $job_cfg->{ids}->{$jobid};
+
+ if (defined($cfg->{'notification-policy'})) {
+ $failed = 1;
+ log_fail("found legacy 'notification-policy' option for job '$jobid'");
+ }
+
+ if (defined($cfg->{'notification-target'})) {
+ $failed = 1;
+ log_fail("found legacy 'notification-target' option for job '$jobid'");
+ }
+ }
+
+ if ($failed) {
+ log_fail(
+ "Changing the backup job configuration via the UI will automatically clear these options."
+ . "Alternatively, you can remove the offending options from /etc/pve/jobs.cfg by hand"
+ );
+ } else {
+ log_pass("No legacy 'notification-policy' or 'notification-target' options found!");
+ }
+}
+
sub check_misc {
print_header("MISCELLANEOUS CHECKS");
my $ssh_config = eval { PVE::Tools::file_get_contents('/root/.ssh/config') };
@@ -1562,6 +1596,7 @@ sub check_misc {
check_bootloader();
check_dkms_modules();
check_legacy_notification_sections();
+ check_legacy_backup_job_options();
}
my sub colored_if {
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-06-24 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 11:33 [pve-devel] [PATCH manager 1/2] cli: pve8to9: check for group and filter sections in notifications.cfg Lukas Wagner
2025-06-24 11:33 ` Lukas Wagner [this message]
2025-07-07 18:39 ` [pve-devel] applied: " 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=20250624113327.134893-2-l.wagner@proxmox.com \
--to=l.wagner@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