From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC ha-manager 1/3] manager: support older versioning schema for ha group migration
Date: Thu, 31 Jul 2025 16:27:17 +0200 [thread overview]
Message-ID: <20250731142749.192813-2-d.kral@proxmox.com> (raw)
In-Reply-To: <20250731142749.192813-1-d.kral@proxmox.com>
Prior to the Proxmox VE 8.x series, the pve-manager is versioned in the
format of `M.m-p`. Versions prior to Proxmox VE 8.x are already EOL'd,
but this change prevents any "Use of uninitialized value" log messages
if one of the nodes is on a version with such a versioning scheme.
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
As discussed with @Thomas off-list, this might not be needed for
production use cases, but I stumbled on it while testing as I thought
pve-statd might still broadcast if someone runs a (unsupported) mixed
version cluster.
src/PVE/HA/Manager.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm
index def63ac0..9d7cb73f 100644
--- a/src/PVE/HA/Manager.pm
+++ b/src/PVE/HA/Manager.pm
@@ -535,7 +535,7 @@ my $have_groups_been_migrated = sub {
my $get_version_parts = sub {
my ($node_version) = @_;
- return $node_version =~ m/^(\d+)\.(\d+)\.(\d+)(?:~(\d+))?/;
+ return $node_version =~ m/^(\d+)\.(\d+)(?:\.|-)(\d+)(?:~(\d+))?/;
};
my $has_node_min_version = sub {
--
2.47.2
_______________________________________________
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-07-31 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 14:27 [pve-devel] [RFC ha-manager 0/3] HA rules follow up (part 1) Daniel Kral
2025-07-31 14:27 ` Daniel Kral [this message]
2025-07-31 14:27 ` [pve-devel] [RFC ha-manager 2/3] manager: fix ~revision version check for ha groups migration Daniel Kral
2025-07-31 14:27 ` [pve-devel] [RFC ha-manager 3/3] test: ha tester: add ha groups migration tests with runtime upgrades Daniel Kral
2025-08-01 16:25 ` [pve-devel] superseded: [RFC ha-manager 0/3] HA rules follow up (part 1) 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=20250731142749.192813-2-d.kral@proxmox.com \
--to=d.kral@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.