Update cluster from 9.1 to 9.2 failed on task [Restart MCollective] (mos_mu playbooks)

[Ilya Bumarskov]

Fuel 9.2 snapshot-id#662
!mos_mu tool was installed from git (https://github.com/aepifanov/mos_mu.git, version date: 22.12.2016)

Steps to reproduce:
   - Deploy 9.1 env with following nodes:
         * Controller
         * Compute, cinder
         * Compute, cinder
   - Apply patch with customization for neutron pkg (Add a comment in version.py)
   - Apply patch with customization for nova conf (Change idle_timeout from 3600 to 3666)
   - 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

[Anton Chevychalov (achevychalov)]

There is the same trouble with systemd that comes to Trusty. We have to fix systemd detection procedure.

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: 9.0
Change author: Anton Chevychalov <email address hidden>
Review: https://review.fuel-infra.org/29522

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/29522
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0

Commit: 82551bf2b8deec174b412fa6eb9c9a3621d579ec
Author: Anton Chevychalov <email address hidden>
Date: Fri Dec 23 10:42:53 2016

Fix systemd detection in service module

There is a trouble with detection of systemd on Ubuntu 14.04
when systemd installed but not used.

Change-Id: I78973f0ec9a79d1ce715676fb2ceb4375133933a
Closes-Bug: #1652247
Releated-Bug: #1648732

[Ilya Bumarskov (ibumarskov)]

Verified on 9.2 snapshot #687.