]> git.proxmox.com Git - pve-ha-manager.git/blob - src/test/test-service-command8/log.expect
manager: refactor fence processing and rework fence-but-no-service log
[pve-ha-manager.git] / src / test / test-service-command8 / 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 noti 20 node1/crm: node 'node3' in fence state but no services to-fence! admin interference?!
14 info 20 node1/crm: got lock 'ha_agent_node3_lock'
15 info 20 node1/crm: fencing: acknowledged - got agent lock for node 'node3'
16 info 20 node1/crm: node 'node3': state changed from 'fence' => 'unknown'
17 emai 20 node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node3'
18 info 21 node1/lrm: got lock 'ha_agent_node1_lock'
19 info 21 node1/lrm: status change wait_for_agent_lock => active
20 info 21 node1/lrm: starting service vm:101
21 info 21 node1/lrm: service status vm:101 started
22 info 22 node2/crm: status change wait_for_quorum => slave
23 info 24 node3/crm: status change wait_for_quorum => slave
24 info 40 node1/crm: node 'node3': state changed from 'unknown' => 'online'
25 info 120 cmdlist: execute service vm:103 add node3 stopped
26 info 120 node1/crm: adding new service 'vm:103' on node 'node3'
27 info 145 node3/lrm: got lock 'ha_agent_node3_lock'
28 info 145 node3/lrm: status change wait_for_agent_lock => active
29 info 160 node1/crm: service 'vm:103': state changed from 'request_stop' to 'stopped'
30 info 220 cmdlist: execute service vm:103 started
31 info 220 node1/crm: service 'vm:103': state changed from 'stopped' to 'started' (node = node3)
32 info 225 node3/lrm: starting service vm:103
33 info 225 node3/lrm: service status vm:103 started
34 info 820 hardware: exit simulation - done