]> git.proxmox.com Git - pve-ha-manager.git/blob - src/test/test-locked-service1/log.expect
manager: set new request_start state for services freshly added to HA
[pve-ha-manager.git] / src / test / test-locked-service1 / 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:103' on node 'node3'
17 info 20 node1/crm: service 'vm:103': state changed from 'request_start' to 'started' (node = node3)
18 info 22 node2/crm: status change wait_for_quorum => slave
19 info 24 node3/crm: status change wait_for_quorum => slave
20 info 25 node3/lrm: got lock 'ha_agent_node3_lock'
21 info 25 node3/lrm: status change wait_for_agent_lock => active
22 info 25 node3/lrm: starting service vm:103
23 info 25 node3/lrm: service status vm:103 started
24 info 120 cmdlist: execute service vm:103 lock
25 info 220 cmdlist: execute network node3 off
26 info 220 node1/crm: node 'node3': state changed from 'online' => 'unknown'
27 info 224 node3/crm: status change slave => wait_for_quorum
28 info 225 node3/lrm: status change active => lost_agent_lock
29 info 260 node1/crm: service 'vm:103': state changed from 'started' to 'fence'
30 info 260 node1/crm: node 'node3': state changed from 'unknown' => 'fence'
31 emai 260 node1/crm: FENCE: Try to fence node 'node3'
32 info 266 watchdog: execute power node3 off
33 info 265 node3/crm: killed by poweroff
34 info 266 node3/lrm: killed by poweroff
35 info 266 hardware: server 'node3' stopped by poweroff (watchdog)
36 info 340 node1/crm: got lock 'ha_agent_node3_lock'
37 info 340 node1/crm: fencing: acknowledged - got agent lock for node 'node3'
38 info 340 node1/crm: node 'node3': state changed from 'fence' => 'unknown'
39 emai 340 node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node3'
40 info 340 node1/crm: service 'vm:103': state changed from 'fence' to 'recovery'
41 info 340 node1/crm: recover service 'vm:103' from fenced node 'node3' to node 'node1'
42 warn 340 node1/crm: removed leftover lock 'backup' from recovered service 'vm:103' to allow its start.
43 info 340 node1/crm: service 'vm:103': state changed from 'recovery' to 'started' (node = node1)
44 info 341 node1/lrm: got lock 'ha_agent_node1_lock'
45 info 341 node1/lrm: status change wait_for_agent_lock => active
46 info 341 node1/lrm: starting service vm:103
47 info 341 node1/lrm: service status vm:103 started
48 info 820 hardware: exit simulation - done