From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 ha-manager 1/2] tests: simulate stale maintainance node caused by simultaneous cluster shutdown
Date: Tue, 13 Jun 2023 09:00:14 +0200 [thread overview]
Message-ID: <f66ff51d-63b5-aa04-56e2-aaf2fdf06153@proxmox.com> (raw)
In-Reply-To: <20230612152711.97078-1-f.ebner@proxmox.com>
Am 12/06/2023 um 17:27 schrieb Fiona Ebner:
> In the test log, it can be seen that the service will unexpectedly be
> migrated back. This is caused by the service's maintainance node
> property being set by the initial shutdown, but never cleared, because
> that currently happens only when the service is started on a different
> node. The next commit will address the issue.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes in v2:
> * Rebase on current master.
> * Split out introducing the test into a dedicated patch.
>
> src/test/test-stale-maintenance-node/cmdlist | 6 ++
> .../datacenter.cfg | 5 +
> .../hardware_status | 5 +
> .../test-stale-maintenance-node/log.expect | 92 +++++++++++++++++++
> .../manager_status | 1 +
> .../service_config | 3 +
> 6 files changed, 112 insertions(+)
> create mode 100644 src/test/test-stale-maintenance-node/cmdlist
> create mode 100644 src/test/test-stale-maintenance-node/datacenter.cfg
> create mode 100644 src/test/test-stale-maintenance-node/hardware_status
> create mode 100644 src/test/test-stale-maintenance-node/log.expect
> create mode 100644 src/test/test-stale-maintenance-node/manager_status
> create mode 100644 src/test/test-stale-maintenance-node/service_config
>
>
applied, thanks!
prev parent reply other threads:[~2023-06-13 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 15:27 [pve-devel] " Fiona Ebner
2023-06-12 15:27 ` [pve-devel] [PATCH v2 ha-manager 2/2] manager: clear stale maintenance " Fiona Ebner
2023-06-13 7:00 ` [pve-devel] applied: " Thomas Lamprecht
2023-06-13 7:00 ` Thomas Lamprecht [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=f66ff51d-63b5-aa04-56e2-aaf2fdf06153@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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