manager: set new request_start state for services freshly added to HA

[pve-ha-manager.git] / src / test / test-recovery4 / 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:102' on node 'node2'
info     20    node1/crm: service 'vm:102': state changed from 'request_start' to 'started'  (node = node2)
info     22    node2/crm: status change wait_for_quorum => slave
info     23    node2/lrm: got lock 'ha_agent_node2_lock'
info     23    node2/lrm: status change wait_for_agent_lock => active
info     23    node2/lrm: starting service vm:102
info     23    node2/lrm: service status vm:102 started
info     24    node3/crm: status change wait_for_quorum => slave
info    120      cmdlist: execute network node2 off
info    120    node1/crm: node 'node2': state changed from 'online' => 'unknown'
info    122    node2/crm: status change slave => wait_for_quorum
info    123    node2/lrm: status change active => lost_agent_lock
info    160    node1/crm: service 'vm:102': state changed from 'started' to 'fence'
info    160    node1/crm: node 'node2': state changed from 'unknown' => 'fence'
emai    160    node1/crm: FENCE: Try to fence node 'node2'
info    164     watchdog: execute power node2 off
info    163    node2/crm: killed by poweroff
info    164    node2/lrm: killed by poweroff
info    164     hardware: server 'node2' stopped by poweroff (watchdog)
info    220      cmdlist: execute delay 0
info    240    node1/crm: got lock 'ha_agent_node2_lock'
info    240    node1/crm: fencing: acknowledged - got agent lock for node 'node2'
info    240    node1/crm: node 'node2': state changed from 'fence' => 'unknown'
emai    240    node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node2'
info    240    node1/crm: service 'vm:102': state changed from 'fence' to 'recovery'
err     240    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     260    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     280    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     300    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
info    320      cmdlist: execute service vm:102 migrate node3
info    320    node1/crm: got crm command: migrate vm:102 node3
err     320    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     340    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     360    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     380    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     400    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
info    420      cmdlist: execute service vm:102 stop 5
info    420    node1/crm: got crm command: stop vm:102 5
err     420    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     440    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     460    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     480    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
err     500    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
info    520      cmdlist: execute service vm:102 disabled
err     520    node1/crm: recovering service 'vm:102' from fenced node 'node2' failed, no recovery node found
info    520    node1/crm: service 'vm:102': state changed from 'recovery' to 'stopped'
info   1120     hardware: exit simulation - done