fix #1378: allow to specify a service shutdown policy

[pve-ha-manager.git] / src / test / test-shutdown1 / log.expect

info      0     hardware: starting simulation
info     20      cmdlist: execute power node1 on
info     20    node1/crm: status change startup => wait_for_quorum
info     20    node1/lrm: status change startup => wait_for_agent_lock
info     20      cmdlist: execute power node2 on
info     20    node2/crm: status change startup => wait_for_quorum
info     20    node2/lrm: status change startup => wait_for_agent_lock
info     20      cmdlist: execute power node3 on
info     20    node3/crm: status change startup => wait_for_quorum
info     20    node3/lrm: status change startup => wait_for_agent_lock
info     20    node1/crm: got lock 'ha_manager_lock'
info     20    node1/crm: status change wait_for_quorum => master
info     20    node1/crm: node 'node1': state changed from 'unknown' => 'online'
info     20    node1/crm: node 'node2': state changed from 'unknown' => 'online'
info     20    node1/crm: node 'node3': state changed from 'unknown' => 'online'
info     20    node1/crm: adding new service 'vm:103' on node 'node3'
info     22    node2/crm: status change wait_for_quorum => slave
info     24    node3/crm: status change wait_for_quorum => slave
info     25    node3/lrm: got lock 'ha_agent_node3_lock'
info     25    node3/lrm: status change wait_for_agent_lock => active
info     25    node3/lrm: starting service vm:103
info     25    node3/lrm: service status vm:103 started
info    120      cmdlist: execute shutdown node3
info    120    node3/lrm: shutdown LRM, stop all services
info    125    node3/lrm: stopping service vm:103
info    125    node3/lrm: service status vm:103 stopped
info    126    node3/lrm: exit (loop end)
info    126     shutdown: execute crm node3 stop
info    125    node3/crm: server received shutdown request
info    145    node3/crm: exit (loop end)
info    145     shutdown: execute power node3 off
info    160    node1/crm: node 'node3': state changed from 'online' => 'unknown'
info    200    node1/crm: service 'vm:103': state changed from 'started' to 'fence'
info    200    node1/crm: node 'node3': state changed from 'unknown' => 'fence'
info    200    node1/crm: got lock 'ha_agent_node3_lock'
info    200    node1/crm: fencing: acknowledged - got agent lock for node 'node3'
info    200    node1/crm: node 'node3': state changed from 'fence' => 'unknown'
info    200    node1/crm: recover service 'vm:103' from fenced node 'node3' to node 'node1'
info    200    node1/crm: service 'vm:103': state changed from 'fence' to 'started'  (node = node1)
info    201    node1/lrm: got lock 'ha_agent_node1_lock'
info    201    node1/lrm: status change wait_for_agent_lock => active
info    201    node1/lrm: starting service vm:103
info    201    node1/lrm: service status vm:103 started
info    720     hardware: exit simulation - done