Comment 0 for bug 1652247

Fuel 9.2 snapshot-id#662

Steps to reproduce:
   - Deploy 9.1 env with following nodes:
         * Controller
         * Compute, cinder
         * Compute, cinder
   - Install mos-playbooks tool on master node (git clone https://github.com/aepifanov/mos_mu.git && git checkout 9.2 && cd mos_mu && ./install_ansible.sh)
   - Execute preparation playbooks (ansible-playbook playbooks/mos9_prepare_fuel.yml && ansible-playbook playbooks/mos9_prepare_env.yml -e '{"env_id":1, "snapshot_repo":"9.0-2016-12-20-174323"}')

Observed behavior:
2016-12-22 20:46:56 - ERROR - ssh_client.py:580 -- Command 'cd mos_mu ; ansible-playbook playbooks/mos9_prepare_env.yml -e '{"env_id":1, "snapshot_repo":"9.0-2016-12-13-154323"}'
' returned exit code 2 while expected [0]
        STDOUT:

<------ output ommited ------>

TASK [Restart MCollective] *****************************************************
fatal: [node-1.test.domain.local]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to get the service status 'mcollective': org.freedesktop.DBus.Error.FileNotFound \
"No such file or directory\""}
fatal: [node-3.test.domain.local]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to get the service status 'mcollective': org.freedesktop.DBus.Error.FileNotFound \
"No such file or directory\""}
fatal: [node-2.test.domain.local]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to get the service status 'mcollective': org.freedesktop.DBus.Error.FileNotFound \
"No such file or directory\""}

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
nailgun.test.domain.local : ok=2 changed=1 unreachable=0 failed=0
node-1.test.domain.local : ok=4 changed=3 unreachable=0 failed=1
node-2.test.domain.local : ok=4 changed=3 unreachable=0 failed=1
node-3.test.domain.local : ok=4 changed=3 unreachable=0 failed=1

root@node-2:~# systemctl status mcollective
mcollective.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

root@node-2:~# status mcollective
mcollective start/running, process 8773