all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH ha-manager v2 4/4] manager: group migration: bulk update changes to resource config
Date: Tue, 20 Jan 2026 09:47:56 +0100	[thread overview]
Message-ID: <20260120084839.103702-5-d.kral@proxmox.com> (raw)
In-Reply-To: <20260120084839.103702-1-d.kral@proxmox.com>

The migration process from HA groups to HA rules might require a lot of
small updates to individual HA resource configs. These updates have been
done per-HA resource, which is quite inefficient and can cause the CRM
to fail to update its watchdog in time.

Even though this is a one-off procedure, it is part of the HA Manager
state machine and must be done in a single action to prevent reading
from an partially updated resource config, i.e., no forking or splitting
the task over multiple HA Manager rounds.

Therefore use the bulk capability of update_service_config(...) to
remove the group fields and migrate the failback flag for all HA
resources in a single read-update-write operation.

Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
changes v1 -> v2:
 - adapted to changes in previous patch

 src/PVE/HA/Manager.pm | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm
index 36a50a4e..2e31296f 100644
--- a/src/PVE/HA/Manager.pm
+++ b/src/PVE/HA/Manager.pm
@@ -579,16 +579,15 @@ my $migrate_group_persistently = sub {
         $haenv->log('notice', "ha groups migration: migration to rules config successful");
 
         PVE::HA::Groups::migrate_groups_to_resources($groups, $resources);
+        my $changes = {};
         for my $sid (keys %$resources) {
             # prevent unnecessary updates for HA resources that do not change
             next if !defined($resources->{$sid}->{group});
 
-            my $changes = {};
             $changes->{$sid} = { param => {}, delete => 'group' };
             $changes->{$sid}->{param}->{failback} = 0 if !$resources->{$sid}->{failback};
-
-            $haenv->update_service_config($changes);
         }
+        $haenv->update_service_config($changes);
         $haenv->log('notice', "ha groups migration: migration to resources config successful");
 
         $haenv->delete_group_config();
-- 
2.47.3



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2026-01-20  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  8:47 [pve-devel] [PATCH-SERIES ha-manager v2 0/4] fix #7133 and improve HA group migration Daniel Kral
2026-01-20  8:47 ` [pve-devel] [PATCH ha-manager v2 1/4] fix #7133: manager: group migration: skip update for resources without group Daniel Kral
2026-01-20  8:47 ` [pve-devel] [PATCH ha-manager v2 2/4] manager: group migration: write only non-default failback values Daniel Kral
2026-01-20  8:47 ` [pve-devel] [PATCH ha-manager v2 3/4] config, env: allow bulk updates with update_service_config Daniel Kral
2026-01-20  8:47 ` Daniel Kral [this message]
2026-01-20 10:35 ` [pve-devel] applied: [PATCH-SERIES ha-manager v2 0/4] fix #7133 and improve HA group migration Fiona Ebner

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=20260120084839.103702-5-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal