From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH FOLLOW-UP ha-manager 0/2] fix errors during persistent migration of HA groups to rules
Date: Wed, 23 Jul 2025 17:37:23 +0200 [thread overview]
Message-ID: <ba6d19f9-966e-42a0-8c6c-9aab5b2f86ae@proxmox.com> (raw)
In-Reply-To: <20250722165428.90281-1-m.koeppl@proxmox.com>
Superseded-by: https://lore.proxmox.com/pve-devel/20250723153524.288508-1-m.koeppl@proxmox.com
On 7/22/25 18:54, Michael Köppl wrote:
> These 2 patches are meant as a follow-up for the HA affinity rules
> series [0]. During testing, I encountered some errors during the
> persistent migration that stopped the entire migration from working.
>
> [0] https://lore.proxmox.com/pve-devel/20250704181659.465441-1-d.kral@proxmox.com/
>
> pve-ha-manager.git:
>
> Michael Köppl (2):
> config: use entire path to groups.cfg path in delete_group_config
> ha: decode JSON string with version info returned by get_node_kv
>
> src/PVE/HA/Config.pm | 3 ++-
> src/PVE/HA/Env/PVE2.pm | 4 +++-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
>
> Summary over all repositories:
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-23 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 16:54 Michael Köppl
2025-07-22 16:54 ` [pve-devel] [PATCH FOLLOW-UP ha-manager 1/2] config: use entire path to groups.cfg path in delete_group_config Michael Köppl
2025-07-22 16:54 ` [pve-devel] [PATCH FOLLOW-UP ha-manager 2/2] ha: decode JSON string with version info returned by get_node_kv Michael Köppl
2025-07-23 15:37 ` Michael Köppl [this message]
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=ba6d19f9-966e-42a0-8c6c-9aab5b2f86ae@proxmox.com \
--to=m.koeppl@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