lrm: also check CRM node-status for determining fence-request

[pve-ha-manager.git] / src / test / test-service-command9 / log.expect

diff --git a/src/test/test-service-command9/log.expect b/src/test/test-service-command9/log.expect
index 79813059a92343935d9d986af6210c9d44500519..40de86bb14e1ac5f5175ab383bb4488ba7f195b2 100644 (file)
--- a/src/test/test-service-command9/log.expect
+++ b/src/test/test-service-command9/log.expect
@@ -15,10 +15,6 @@ info     20    node1/lrm: got lock 'ha_agent_node1_lock'
 info     20    node1/lrm: status change wait_for_agent_lock => active
 info     20    node1/lrm: starting service vm:101
 info     20    node1/lrm: service status vm:101 started
-info     22    node3/lrm: got lock 'ha_agent_node3_lock'
-info     22    node3/lrm: status change wait_for_agent_lock => active
-info     22    node3/lrm: starting service vm:103
-info     22    node3/lrm: service status vm:103 started
 info     40     run-loop: skipping CRM round
 info     60    node1/crm: got lock 'ha_manager_lock'
 info     60    node1/crm: status change wait_for_quorum => master