]> git.proxmox.com Git - pve-ha-manager.git/blame - src/test/test-recovery2/log.expect
test/sim: also log delay commands
[pve-ha-manager.git] / src / test / test-recovery2 / log.expect
CommitLineData
90a24755
TL
1info 0 hardware: starting simulation
2info 20 cmdlist: execute power node1 on
3info 20 node1/crm: status change startup => wait_for_quorum
4info 20 node1/lrm: status change startup => wait_for_agent_lock
5info 20 cmdlist: execute power node2 on
6info 20 node2/crm: status change startup => wait_for_quorum
7info 20 node2/lrm: status change startup => wait_for_agent_lock
8info 20 cmdlist: execute power node3 on
9info 20 node3/crm: status change startup => wait_for_quorum
10info 20 node3/lrm: status change startup => wait_for_agent_lock
11info 20 node1/crm: got lock 'ha_manager_lock'
12info 20 node1/crm: status change wait_for_quorum => master
13info 20 node1/crm: node 'node1': state changed from 'unknown' => 'online'
14info 20 node1/crm: node 'node2': state changed from 'unknown' => 'online'
15info 20 node1/crm: node 'node3': state changed from 'unknown' => 'online'
16info 20 node1/crm: adding new service 'vm:102' on node 'node2'
17info 22 node2/crm: status change wait_for_quorum => slave
18info 23 node2/lrm: got lock 'ha_agent_node2_lock'
19info 23 node2/lrm: status change wait_for_agent_lock => active
20info 23 node2/lrm: starting service vm:102
21info 23 node2/lrm: service status vm:102 started
22info 24 node3/crm: status change wait_for_quorum => slave
23info 120 cmdlist: execute network node2 off
24info 120 node1/crm: node 'node2': state changed from 'online' => 'unknown'
25info 122 node2/crm: status change slave => wait_for_quorum
26info 123 node2/lrm: status change active => lost_agent_lock
27info 160 node1/crm: service 'vm:102': state changed from 'started' to 'fence'
28info 160 node1/crm: node 'node2': state changed from 'unknown' => 'fence'
29emai 160 node1/crm: FENCE: Try to fence node 'node2'
30info 164 watchdog: execute power node2 off
31info 163 node2/crm: killed by poweroff
32info 164 node2/lrm: killed by poweroff
33info 164 hardware: server 'node2' stopped by poweroff (watchdog)
fe19c9b4 34info 220 cmdlist: execute delay 0
90a24755
TL
35info 240 node1/crm: got lock 'ha_agent_node2_lock'
36info 240 node1/crm: fencing: acknowledged - got agent lock for node 'node2'
37info 240 node1/crm: node 'node2': state changed from 'fence' => 'unknown'
38emai 240 node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node2'
39info 240 node1/crm: service 'vm:102': state changed from 'fence' to 'recovery'
40err 240 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
41err 260 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
42err 280 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
43err 300 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 44info 320 cmdlist: execute delay 0
90a24755
TL
45err 320 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
46err 340 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
47err 360 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
48err 380 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
49err 400 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 50info 420 cmdlist: execute delay 0
90a24755
TL
51err 420 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
52err 440 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
53err 460 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
54err 480 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
55err 500 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 56info 520 cmdlist: execute delay 0
90a24755
TL
57err 520 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
58err 540 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
59err 560 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
60err 580 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
61err 600 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 62info 620 cmdlist: execute delay 0
90a24755
TL
63err 620 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
64err 640 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
65err 660 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
66err 680 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
67err 700 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 68info 720 cmdlist: execute delay 0
90a24755
TL
69err 720 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
70err 740 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
71err 760 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
72err 780 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
73err 800 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 74info 820 cmdlist: execute delay 0
90a24755
TL
75err 820 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
76err 840 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
77err 860 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
78err 880 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
79err 900 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 80info 920 cmdlist: execute delay 0
90a24755
TL
81err 920 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
82err 940 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
83err 960 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
84err 980 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
85err 1000 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 86info 1020 cmdlist: execute delay 0
90a24755
TL
87err 1020 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
88err 1040 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
89err 1060 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
90err 1080 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
91err 1100 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
fe19c9b4 92info 1120 cmdlist: execute delay 0
90a24755
TL
93err 1120 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
94err 1140 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
95err 1160 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
96err 1180 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
97err 1200 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
98info 1220 cmdlist: execute power node2 on
99info 1220 node2/crm: status change startup => wait_for_quorum
100info 1220 node2/lrm: status change startup => wait_for_agent_lock
101info 1220 cmdlist: execute network node2 on
102info 1220 node1/crm: node 'node2': state changed from 'unknown' => 'online'
103info 1220 node1/crm: recover service 'vm:102' to previous failed and fenced node 'node2' again
104info 1220 node1/crm: service 'vm:102': state changed from 'recovery' to 'started' (node = node2)
105info 1222 node2/crm: status change wait_for_quorum => slave
106info 1223 node2/lrm: got lock 'ha_agent_node2_lock'
107info 1223 node2/lrm: status change wait_for_agent_lock => active
108info 1223 node2/lrm: starting service vm:102
109info 1223 node2/lrm: service status vm:102 started
110info 1820 hardware: exit simulation - done