]> git.proxmox.com Git - pve-ha-manager.git/blob - src/test/test-basic2/log.expect
manager: make recovery actual state in FSM
[pve-ha-manager.git] / src / test / test-basic2 / 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 node3 on
6 info 20 node3/crm: status change startup => wait_for_quorum
7 info 20 node3/lrm: status change startup => wait_for_agent_lock
8 info 22 node3/crm: got lock 'ha_manager_lock'
9 info 22 node3/crm: status change wait_for_quorum => master
10 info 22 node3/crm: node 'node2': state changed from 'online' => 'unknown'
11 info 22 node3/crm: got lock 'ha_agent_node1_lock'
12 info 22 node3/crm: fencing: acknowledged - got agent lock for node 'node1'
13 info 22 node3/crm: node 'node1': state changed from 'fence' => 'unknown'
14 emai 22 node3/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node1'
15 info 22 node3/crm: service 'vm:101': state changed from 'fence' to 'recovery'
16 info 22 node3/crm: recover service 'vm:101' from fenced node 'node1' to node 'node3'
17 info 22 node3/crm: service 'vm:101': state changed from 'recovery' to 'started' (node = node3)
18 info 23 node3/lrm: got lock 'ha_agent_node3_lock'
19 info 23 node3/lrm: status change wait_for_agent_lock => active
20 info 23 node3/lrm: starting service vm:101
21 info 23 node3/lrm: service status vm:101 started
22 info 40 node1/crm: status change wait_for_quorum => slave
23 info 42 node3/crm: node 'node1': state changed from 'unknown' => 'online'
24 info 620 hardware: exit simulation - done