]> git.proxmox.com Git - pve-ha-manager.git/blob - src/test/test-basic1/log.expect
Fix #1189: correct spelling in fence mail
[pve-ha-manager.git] / src / test / test-basic1 / 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 node1/crm: got lock 'ha_manager_lock'
12 info 20 node1/crm: status change wait_for_quorum => master
13 info 20 node1/crm: node 'node1': state changed from 'unknown' => 'online'
14 info 20 node1/crm: node 'node2': state changed from 'unknown' => 'online'
15 info 20 node1/crm: node 'node3': state changed from 'unknown' => 'online'
16 info 20 node1/crm: adding new service 'vm:101' on node 'node1'
17 info 20 node1/crm: adding new service 'vm:102' on node 'node2'
18 info 20 node1/crm: adding new service 'vm:103' on node 'node3'
19 info 20 node1/crm: service 'vm:102': state changed from 'started' to 'request_stop'
20 info 21 node1/lrm: got lock 'ha_agent_node1_lock'
21 info 21 node1/lrm: status change wait_for_agent_lock => active
22 info 21 node1/lrm: starting service vm:101
23 info 21 node1/lrm: service status vm:101 started
24 info 22 node2/crm: status change wait_for_quorum => slave
25 info 23 node2/lrm: got lock 'ha_agent_node2_lock'
26 info 23 node2/lrm: status change wait_for_agent_lock => active
27 info 24 node3/crm: status change wait_for_quorum => slave
28 info 25 node3/lrm: got lock 'ha_agent_node3_lock'
29 info 25 node3/lrm: status change wait_for_agent_lock => active
30 info 25 node3/lrm: starting service vm:103
31 info 25 node3/lrm: service status vm:103 started
32 info 40 node1/crm: service 'vm:102': state changed from 'request_stop' to 'stopped'
33 info 120 cmdlist: execute network node3 off
34 info 120 node1/crm: node 'node3': state changed from 'online' => 'unknown'
35 info 124 node3/crm: status change slave => wait_for_quorum
36 info 125 node3/lrm: status change active => lost_agent_lock
37 info 160 node1/crm: service 'vm:103': state changed from 'started' to 'fence'
38 info 160 node1/crm: node 'node3': state changed from 'unknown' => 'fence'
39 info 166 watchdog: execute power node3 off
40 info 165 node3/crm: killed by poweroff
41 info 166 node3/lrm: killed by poweroff
42 info 166 hardware: server 'node3' stopped by poweroff (watchdog)
43 info 240 node1/crm: got lock 'ha_agent_node3_lock'
44 info 240 node1/crm: fencing: acknowledged - got agent lock for node 'node3'
45 info 240 node1/crm: node 'node3': state changed from 'fence' => 'unknown'
46 info 240 node1/crm: recover service 'vm:103' from fenced node 'node3' to node 'node2'
47 info 240 node1/crm: service 'vm:103': state changed from 'fence' to 'started' (node = node2)
48 info 243 node2/lrm: starting service vm:103
49 info 243 node2/lrm: service status vm:103 started
50 info 720 hardware: exit simulation - done