From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 2/2] cli: pve8to9: check for group and filter sections in notifications.cfg
Date: Tue, 27 May 2025 11:41:11 +0200 [thread overview]
Message-ID: <20250527094111.194446-2-l.wagner@proxmox.com> (raw)
In-Reply-To: <20250527094111.194446-1-l.wagner@proxmox.com>
The notification stack removes these sections automatically whenever the
configuration is updated, so this should only affect a small number of
people - those who used the notification system while it was only
available in pvetest, created a filter/group and never changed the
configuration afterwards.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
PVE/CLI/pve8to9.pm | 37 +++++++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/PVE/CLI/pve8to9.pm b/PVE/CLI/pve8to9.pm
index 42b7073b..9d00e064 100644
--- a/PVE/CLI/pve8to9.pm
+++ b/PVE/CLI/pve8to9.pm
@@ -1372,6 +1372,42 @@ sub check_dkms_modules {
}
}
+sub check_legacy_notification_sections {
+ log_info("Check for legacy 'filter' or 'group' sections in /etc/pve/notifications.cfg...");
+
+ my $raw = eval { PVE::Tools::file_get_contents("/etc/pve/notifications.cfg") };
+ return if !defined($raw);
+
+ my $failed = 0;
+ my @lines = split(/\n/, $raw);
+
+ for my $line (@lines) {
+ # Any line in a section config is either a comment (starts with #), a
+ # section header (starts with the section type, without any leading
+ # space) or is a property indented by whitespace. This means we
+ # should be able to reliably detect the legacy sections by just
+ # checking the start of the line.
+
+ if ($line =~ /^filter/) {
+ $failed = 1;
+ log_fail("found legacy 'filter' section: $line");
+ }
+
+ if ($line =~ /^group/) {
+ $failed = 1;
+ log_fail("found legacy 'group' section: $line");
+ }
+ }
+
+ if ($failed) {
+ log_fail("Any modification to the notification configuration via the API or Web UI will"
+ . " automatically remove these sections. Alternatively, you can remove the offending"
+ . " sections by hand from /etc/pve/notifications.cfg.");
+ } else {
+ log_pass("No legacy 'filter' or 'group' sections found!");
+ }
+}
+
sub check_misc {
print_header("MISCELLANEOUS CHECKS");
my $ssh_config = eval { PVE::Tools::file_get_contents('/root/.ssh/config') };
@@ -1474,6 +1510,7 @@ sub check_misc {
check_nvidia_vgpu_service();
check_bootloader();
check_dkms_modules();
+ check_legacy_notification_sections();
}
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-05-27 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 9:41 [pve-devel] [PATCH manager 1/2] cli: copy pve7to8 to pve8to9 Lukas Wagner
2025-05-27 9:41 ` Lukas Wagner [this message]
2025-05-27 11:42 ` Daniel Kral
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=20250527094111.194446-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.