]> git.proxmox.com Git - pve-ha-manager.git/blame - src/test/test-basic1/log.expect
manager: set new request_start state for services freshly added to HA
[pve-ha-manager.git] / src / test / test-basic1 / log.expect
CommitLineData
d5b62196
DM
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'
eda9314d
DM
16info 20 node1/crm: adding new service 'vm:101' on node 'node1'
17info 20 node1/crm: adding new service 'vm:102' on node 'node2'
18info 20 node1/crm: adding new service 'vm:103' on node 'node3'
c2f2b9c6
TL
19info 20 node1/crm: service 'vm:101': state changed from 'request_start' to 'started' (node = node1)
20info 20 node1/crm: service 'vm:103': state changed from 'request_start' to 'started' (node = node3)
d5b62196
DM
21info 21 node1/lrm: got lock 'ha_agent_node1_lock'
22info 21 node1/lrm: status change wait_for_agent_lock => active
eda9314d
DM
23info 21 node1/lrm: starting service vm:101
24info 21 node1/lrm: service status vm:101 started
d5b62196
DM
25info 22 node2/crm: status change wait_for_quorum => slave
26info 23 node2/lrm: got lock 'ha_agent_node2_lock'
27info 23 node2/lrm: status change wait_for_agent_lock => active
28info 24 node3/crm: status change wait_for_quorum => slave
29info 25 node3/lrm: got lock 'ha_agent_node3_lock'
30info 25 node3/lrm: status change wait_for_agent_lock => active
eda9314d
DM
31info 25 node3/lrm: starting service vm:103
32info 25 node3/lrm: service status vm:103 started
24678a59 33info 40 node1/crm: service 'vm:102': state changed from 'request_stop' to 'stopped'
d5b62196
DM
34info 120 cmdlist: execute network node3 off
35info 120 node1/crm: node 'node3': state changed from 'online' => 'unknown'
36info 124 node3/crm: status change slave => wait_for_quorum
37info 125 node3/lrm: status change active => lost_agent_lock
24678a59 38info 160 node1/crm: service 'vm:103': state changed from 'started' to 'fence'
ceac1930 39info 160 node1/crm: node 'node3': state changed from 'unknown' => 'fence'
3220c339 40emai 160 node1/crm: FENCE: Try to fence node 'node3'
d5b62196
DM
41info 166 watchdog: execute power node3 off
42info 165 node3/crm: killed by poweroff
43info 166 node3/lrm: killed by poweroff
44info 166 hardware: server 'node3' stopped by poweroff (watchdog)
45info 240 node1/crm: got lock 'ha_agent_node3_lock'
e2a7b1b5 46info 240 node1/crm: fencing: acknowledged - got agent lock for node 'node3'
d5b62196 47info 240 node1/crm: node 'node3': state changed from 'fence' => 'unknown'
3220c339 48emai 240 node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node3'
c259b1a8 49info 240 node1/crm: service 'vm:103': state changed from 'fence' to 'recovery'
9da84a0d 50info 240 node1/crm: recover service 'vm:103' from fenced node 'node3' to node 'node2'
c259b1a8 51info 240 node1/crm: service 'vm:103': state changed from 'recovery' to 'started' (node = node2)
9da84a0d
TL
52info 243 node2/lrm: starting service vm:103
53info 243 node2/lrm: service status vm:103 started
d5b62196 54info 720 hardware: exit simulation - done