]> git.proxmox.com Git - pve-ha-manager.git/blame - src/test/test-crs-static1/log.expect
test: add tests for static resource scheduling
[pve-ha-manager.git] / src / test / test-crs-static1 / log.expect
CommitLineData
f348399f
FE
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: using scheduler mode 'static'
14info 20 node1/crm: node 'node1': state changed from 'unknown' => 'online'
15info 20 node1/crm: node 'node2': state changed from 'unknown' => 'online'
16info 20 node1/crm: node 'node3': state changed from 'unknown' => 'online'
17info 20 node1/crm: adding new service 'vm:102' on node 'node1'
18info 21 node1/lrm: got lock 'ha_agent_node1_lock'
19info 21 node1/lrm: status change wait_for_agent_lock => active
20info 21 node1/lrm: starting service vm:102
21info 21 node1/lrm: service status vm:102 started
22info 22 node2/crm: status change wait_for_quorum => slave
23info 24 node3/crm: status change wait_for_quorum => slave
24info 120 cmdlist: execute network node1 off
25info 120 node1/crm: status change master => lost_manager_lock
26info 120 node1/crm: status change lost_manager_lock => wait_for_quorum
27info 121 node1/lrm: status change active => lost_agent_lock
28info 162 watchdog: execute power node1 off
29info 161 node1/crm: killed by poweroff
30info 162 node1/lrm: killed by poweroff
31info 162 hardware: server 'node1' stopped by poweroff (watchdog)
32info 222 node3/crm: got lock 'ha_manager_lock'
33info 222 node3/crm: status change slave => master
34info 222 node3/crm: using scheduler mode 'static'
35info 222 node3/crm: node 'node1': state changed from 'online' => 'unknown'
36info 282 node3/crm: service 'vm:102': state changed from 'started' to 'fence'
37info 282 node3/crm: node 'node1': state changed from 'unknown' => 'fence'
38emai 282 node3/crm: FENCE: Try to fence node 'node1'
39info 282 node3/crm: got lock 'ha_agent_node1_lock'
40info 282 node3/crm: fencing: acknowledged - got agent lock for node 'node1'
41info 282 node3/crm: node 'node1': state changed from 'fence' => 'unknown'
42emai 282 node3/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node1'
43info 282 node3/crm: service 'vm:102': state changed from 'fence' to 'recovery'
44info 282 node3/crm: recover service 'vm:102' from fenced node 'node1' to node 'node3'
45info 282 node3/crm: service 'vm:102': state changed from 'recovery' to 'started' (node = node3)
46info 283 node3/lrm: got lock 'ha_agent_node3_lock'
47info 283 node3/lrm: status change wait_for_agent_lock => active
48info 283 node3/lrm: starting service vm:102
49info 283 node3/lrm: service status vm:102 started
50info 720 hardware: exit simulation - done