From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH ha-manager 1/2] test: add maintenance test case with stuck HA resource
Date: Wed, 8 Jul 2026 10:42:04 +0200 [thread overview]
Message-ID: <20260708084205.69947-2-d.kral@proxmox.com> (raw)
In-Reply-To: <20260708084205.69947-1-d.kral@proxmox.com>
This test case documents the current behavior of a node being stuck in
maintenance state even after lifting the maintenance request on that
node if at least one HA resource is kept stuck on the node as it cannot
migrate to another node.
This behavior will be changed by an upcoming patch.
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
src/test/test-crm-maintenance-request5/README | 7 +++
.../test-crm-maintenance-request5/cmdlist | 5 ++
.../hardware_status | 5 ++
.../test-crm-maintenance-request5/log.expect | 57 +++++++++++++++++++
.../manager_status | 1 +
.../service_config | 3 +
6 files changed, 78 insertions(+)
create mode 100644 src/test/test-crm-maintenance-request5/README
create mode 100644 src/test/test-crm-maintenance-request5/cmdlist
create mode 100644 src/test/test-crm-maintenance-request5/hardware_status
create mode 100644 src/test/test-crm-maintenance-request5/log.expect
create mode 100644 src/test/test-crm-maintenance-request5/manager_status
create mode 100644 src/test/test-crm-maintenance-request5/service_config
diff --git a/src/test/test-crm-maintenance-request5/README b/src/test/test-crm-maintenance-request5/README
new file mode 100644
index 00000000..e7fe0d5e
--- /dev/null
+++ b/src/test/test-crm-maintenance-request5/README
@@ -0,0 +1,7 @@
+Test setting the maintenance mode for a node where an HA resource cannot be
+moved to any other node because of migration errors and moving it out of
+maintenance mode again.
+
+Currently, the node will move out of the maintenance mode, but is left stuck in
+maintenance state as it never reached the required state to be empty to be able
+to move to active state again after the maintenance request is lifted.
diff --git a/src/test/test-crm-maintenance-request5/cmdlist b/src/test/test-crm-maintenance-request5/cmdlist
new file mode 100644
index 00000000..5aa42a6c
--- /dev/null
+++ b/src/test/test-crm-maintenance-request5/cmdlist
@@ -0,0 +1,5 @@
+[
+ [ "power node1 on", "power node2 on", "power node3 on" ],
+ [ "crm node1 enable-node-maintenance" ],
+ [ "crm node1 disable-node-maintenance" ]
+]
diff --git a/src/test/test-crm-maintenance-request5/hardware_status b/src/test/test-crm-maintenance-request5/hardware_status
new file mode 100644
index 00000000..451beb13
--- /dev/null
+++ b/src/test/test-crm-maintenance-request5/hardware_status
@@ -0,0 +1,5 @@
+{
+ "node1": { "power": "off", "network": "off" },
+ "node2": { "power": "off", "network": "off" },
+ "node3": { "power": "off", "network": "off" }
+}
diff --git a/src/test/test-crm-maintenance-request5/log.expect b/src/test/test-crm-maintenance-request5/log.expect
new file mode 100644
index 00000000..90326ef5
--- /dev/null
+++ b/src/test/test-crm-maintenance-request5/log.expect
@@ -0,0 +1,57 @@
+info 0 hardware: starting simulation
+info 20 cmdlist: execute power node1 on
+info 20 node1/crm: status change startup => wait_for_quorum
+info 20 node1/lrm: status change startup => wait_for_agent_lock
+info 20 cmdlist: execute power node2 on
+info 20 node2/crm: status change startup => wait_for_quorum
+info 20 node2/lrm: status change startup => wait_for_agent_lock
+info 20 cmdlist: execute power node3 on
+info 20 node3/crm: status change startup => wait_for_quorum
+info 20 node3/lrm: status change startup => wait_for_agent_lock
+info 20 node1/crm: got lock 'ha_manager_lock'
+info 20 node1/crm: status change wait_for_quorum => master
+info 20 node1/crm: node 'node1': state changed from 'unknown' => 'online'
+info 20 node1/crm: node 'node2': state changed from 'unknown' => 'online'
+info 20 node1/crm: node 'node3': state changed from 'unknown' => 'online'
+info 20 node1/crm: adding new service 'fa:109' on node 'node1'
+info 20 node1/crm: service 'fa:109': state changed from 'request_start' to 'started' (node = node1)
+info 21 node1/lrm: got lock 'ha_agent_node1_lock'
+info 21 node1/lrm: status change wait_for_agent_lock => active
+info 21 node1/lrm: starting service fa:109
+info 21 node1/lrm: service status fa:109 started
+info 22 node2/crm: status change wait_for_quorum => slave
+info 24 node3/crm: status change wait_for_quorum => slave
+info 120 cmdlist: execute crm node1 enable-node-maintenance
+info 121 node1/lrm: status change active => maintenance
+info 140 node1/crm: node 'node1': state changed from 'online' => 'maintenance'
+info 140 node1/crm: relocate service 'fa:109' to node 'node2'
+info 140 node1/crm: service 'fa:109': state changed from 'started' to 'relocate' (node = node1, target = node2)
+err 141 node1/lrm: service fa:109 not moved (migration error)
+info 143 node2/lrm: got lock 'ha_agent_node2_lock'
+info 143 node2/lrm: status change wait_for_agent_lock => active
+err 160 node1/crm: service 'fa:109' - migration failed (exit code 1)
+info 160 node1/crm: service 'fa:109': state changed from 'relocate' to 'started' (node = node1)
+info 160 node1/crm: relocate service 'fa:109' to node 'node2'
+info 160 node1/crm: service 'fa:109': state changed from 'started' to 'relocate' (node = node1, target = node2)
+err 161 node1/lrm: service fa:109 not moved (migration error)
+err 180 node1/crm: service 'fa:109' - migration failed (exit code 1)
+info 180 node1/crm: service 'fa:109': state changed from 'relocate' to 'started' (node = node1)
+info 180 node1/crm: relocate service 'fa:109' to node 'node2'
+info 180 node1/crm: service 'fa:109': state changed from 'started' to 'relocate' (node = node1, target = node2)
+err 181 node1/lrm: service fa:109 not moved (migration error)
+err 200 node1/crm: service 'fa:109' - migration failed (exit code 1)
+info 200 node1/crm: service 'fa:109': state changed from 'relocate' to 'started' (node = node1)
+info 200 node1/crm: relocate service 'fa:109' to node 'node2'
+info 200 node1/crm: service 'fa:109': state changed from 'started' to 'relocate' (node = node1, target = node2)
+err 201 node1/lrm: service fa:109 not moved (migration error)
+info 220 cmdlist: execute crm node1 disable-node-maintenance
+err 220 node1/crm: service 'fa:109' - migration failed (exit code 1)
+info 220 node1/crm: service 'fa:109': state changed from 'relocate' to 'started' (node = node1)
+info 220 node1/crm: relocate service 'fa:109' to node 'node2'
+info 220 node1/crm: service 'fa:109': state changed from 'started' to 'relocate' (node = node1, target = node2)
+err 221 node1/lrm: service fa:109 not moved (migration error)
+info 240 node1/crm: node 'node1': state changed from 'maintenance' => 'online'
+err 240 node1/crm: service 'fa:109' - migration failed (exit code 1)
+info 240 node1/crm: service 'fa:109': state changed from 'relocate' to 'started' (node = node1)
+info 240 node1/crm: service 'fa:109': clearing stale maintenance node 'node1' setting (is current node)
+info 820 hardware: exit simulation - done
diff --git a/src/test/test-crm-maintenance-request5/manager_status b/src/test/test-crm-maintenance-request5/manager_status
new file mode 100644
index 00000000..0967ef42
--- /dev/null
+++ b/src/test/test-crm-maintenance-request5/manager_status
@@ -0,0 +1 @@
+{}
diff --git a/src/test/test-crm-maintenance-request5/service_config b/src/test/test-crm-maintenance-request5/service_config
new file mode 100644
index 00000000..78879193
--- /dev/null
+++ b/src/test/test-crm-maintenance-request5/service_config
@@ -0,0 +1,3 @@
+{
+ "fa:109": { "node": "node1", "state": "started" }
+}
--
2.47.3
next prev parent reply other threads:[~2026-07-08 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 8:42 [PATCH-SERIES ha-manager 0/2] fix #6084: allow dropping maintenance state with active HA resources Daniel Kral
2026-07-08 8:42 ` Daniel Kral [this message]
2026-07-08 8:42 ` [PATCH ha-manager 2/2] fix #6084: lrm: allow dropping maintenance " Daniel Kral
2026-07-08 14:40 ` Michael Köppl
2026-07-08 14:40 ` [PATCH-SERIES ha-manager 0/2] fix #6084: allow dropping maintenance state " Michael Köppl
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=20260708084205.69947-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.