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

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

diff --git a/src/test/test-service-command8/log.expect b/src/test/test-service-command8/log.expect
index 572e2f256f31fa8caa88e3aca9bb58396caa4ca4..72eb36923d51dbb8518e45c65c3648ed4f07d03d 100644 (file)
--- a/src/test/test-service-command8/log.expect
+++ b/src/test/test-service-command8/log.expect
@@ -18,11 +18,5 @@ info     22    node2/crm: status change wait_for_quorum => slave
 info     24    node3/crm: status change wait_for_quorum => slave
 info    120      cmdlist: execute service vm:103 add node3 stopped
 info    120    node1/crm: adding new service 'vm:103' on node 'node3'
-info    125    node3/lrm: got lock 'ha_agent_node3_lock'
-info    125    node3/lrm: status change wait_for_agent_lock => active
-info    140    node1/crm: service 'vm:103': state changed from 'request_stop' to 'stopped'
 info    220      cmdlist: execute service vm:103 started
-info    220    node1/crm: service 'vm:103': state changed from 'stopped' to 'started'  (node = node3)
-info    225    node3/lrm: starting service vm:103
-info    225    node3/lrm: service status vm:103 started
 info    820     hardware: exit simulation - done