]> git.proxmox.com Git - pve-ha-manager.git/blame - src/test/test-recovery1/log.expect
manager: set new request_start state for services freshly added to HA
[pve-ha-manager.git] / src / test / test-recovery1 / log.expect
CommitLineData
08aa53c2
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'
c2f2b9c6 17info 20 node1/crm: service 'vm:102': state changed from 'request_start' to 'started' (node = node2)
08aa53c2
TL
18info 22 node2/crm: status change wait_for_quorum => slave
19info 23 node2/lrm: got lock 'ha_agent_node2_lock'
20info 23 node2/lrm: status change wait_for_agent_lock => active
21info 23 node2/lrm: starting service vm:102
22info 23 node2/lrm: service status vm:102 started
23info 24 node3/crm: status change wait_for_quorum => slave
24info 120 cmdlist: execute network node2 off
25info 120 node1/crm: node 'node2': state changed from 'online' => 'unknown'
26info 122 node2/crm: status change slave => wait_for_quorum
27info 123 node2/lrm: status change active => lost_agent_lock
28info 160 node1/crm: service 'vm:102': state changed from 'started' to 'fence'
29info 160 node1/crm: node 'node2': state changed from 'unknown' => 'fence'
3220c339 30emai 160 node1/crm: FENCE: Try to fence node 'node2'
08aa53c2
TL
31info 164 watchdog: execute power node2 off
32info 163 node2/crm: killed by poweroff
33info 164 node2/lrm: killed by poweroff
34info 164 hardware: server 'node2' stopped by poweroff (watchdog)
35info 240 node1/crm: got lock 'ha_agent_node2_lock'
e2a7b1b5 36info 240 node1/crm: fencing: acknowledged - got agent lock for node 'node2'
08aa53c2 37info 240 node1/crm: node 'node2': state changed from 'fence' => 'unknown'
3220c339 38emai 240 node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node2'
c259b1a8 39info 240 node1/crm: service 'vm:102': state changed from 'fence' to 'recovery'
08aa53c2 40err 240 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
90a24755
TL
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
44err 320 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
45err 340 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
46err 360 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
47err 380 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
48err 400 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
49err 420 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
50err 440 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
51err 460 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
52err 480 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
53err 500 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
54err 520 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
55err 540 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
56err 560 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
57err 580 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
58err 600 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
59err 620 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
60err 640 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
61err 660 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
62err 680 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
63err 700 node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
08aa53c2 64info 720 hardware: exit simulation - done