all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Daniel Kral" <d.kral@proxmox.com>
To: "Daniel Kral" <d.kral@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH-SERIES ha-manager 0/7] improve handling of maintenance nodes
Date: Fri, 06 Nov 2026 10:58:08 +0100	[thread overview]
Message-ID: <DMO1F7QW958G.ZR44RA731ZQ6@proxmox.com> (raw)
In-Reply-To: <20260422100035.232716-1-d.kral@proxmox.com>

Superseded-by: https://lore.proxmox.com/pve-devel/20261106095650.72865-1-d.kral@proxmox.com/

On Wed Apr 22, 2026 at 12:00 PM CEST, Daniel Kral wrote:
> As reported by a recent Proxmox forum post [0], there are some cases
> where either HA resources are not moved away from maintenance nodes or
> are not moved back to the maintenance nodes after these are put out of
> maintenance again.
>
> Even though we cannot resolve all situations (for example, the affinity
> rules constrain the HA resource so that it cannot be moved anywhere but
> the maintenance node), this patch series improves the handling with:
>
> - log warnings if HA resources cannot be moved to a replacement node
> - make HA resources with fallback enabled move back to their previous
>   maintenance node
> - make HA resource bundles move back to their previous maintenance node
> - try all available, effective priority classes for an HA resource while
>   applying the negative resource affinity rules
>
> The last change makes the system more consistent overall, but might
> introduce some unintended node placements in highly constrained
> scenarios because of how the HA Manager currently resolves these node
> placements individually per-HA resource. This should be improved upon in
> a future patch series (this bugzilla entry [1] might also be relevant).
>
> [0] https://forum.proxmox.com/threads/182890/
> [1] https://bugzilla.proxmox.com/show_bug.cgi?id=7475




      parent reply	other threads:[~2026-11-06  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 10:00 [PATCH-SERIES ha-manager 0/7] improve handling of maintenance nodes Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 1/7] manager: warn if HA resources cannot be moved away from maintenance node Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 2/7] test: add test casses for node affinity rules with maintenance mode Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 3/7] test: add test cases for resource " Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 4/7] manager: make HA resources without failback move back to maintenance node Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 5/7] manager: make HA resource bundles " Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 6/7] make get_node_affinity return all priority classes sorted in descending order Daniel Kral
2026-10-29  8:43   ` Daniel Kral
2026-04-22 10:00 ` [PATCH ha-manager 7/7] manager: try multiple priority classes when applying negative resource affinity Daniel Kral
2026-04-29 16:58   ` Michael Köppl
2026-10-29  9:32     ` Daniel Kral
2026-11-06  9:58 ` Daniel Kral [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=DMO1F7QW958G.ZR44RA731ZQ6@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