]> git.proxmox.com Git - pve-ha-manager.git/blob - src/test/test-service-command9/log.expect
lrm: also check CRM node-status for determining fence-request
[pve-ha-manager.git] / src / test / test-service-command9 / log.expect
1 info 0 hardware: starting simulation
2 info 20 cmdlist: execute power node1 on
3 info 20 node1/crm: status change startup => wait_for_quorum
4 info 20 node1/lrm: status change startup => wait_for_agent_lock
5 info 20 cmdlist: execute power node2 on
6 info 20 node2/crm: status change startup => wait_for_quorum
7 info 20 node2/lrm: status change startup => wait_for_agent_lock
8 info 20 cmdlist: execute power node3 on
9 info 20 node3/crm: status change startup => wait_for_quorum
10 info 20 node3/lrm: status change startup => wait_for_agent_lock
11 info 20 cmdlist: execute skip-round crm 2
12 info 20 cmdlist: execute service vm:103 started
13 info 20 run-loop: skipping CRM round
14 info 20 node1/lrm: got lock 'ha_agent_node1_lock'
15 info 20 node1/lrm: status change wait_for_agent_lock => active
16 info 20 node1/lrm: starting service vm:101
17 info 20 node1/lrm: service status vm:101 started
18 info 40 run-loop: skipping CRM round
19 info 60 node1/crm: got lock 'ha_manager_lock'
20 info 60 node1/crm: status change wait_for_quorum => master
21 info 62 node2/crm: status change wait_for_quorum => slave
22 info 64 node3/crm: status change wait_for_quorum => slave
23 info 620 hardware: exit simulation - done