4.27 Deployment Fails With a "Command Failed" Error

If the Docker Engine is not running on a target node when you deploy OpenStack, the deployment fails with a Command failed error when starting the Ansible container, for example:

TASK [common : Starting Ansible container]
fatal: [ol7-c4]: FAILED! => {"changed": false, "failed": true, "msg":
"ConnectionError(ProtocolError('Connection aborted.', error(2, 'No such file or directory')),)"}

ol7-c4                     : ok=3    changed=0    unreachable=0    failed=1
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/kollacli/commands/deploy.py", line66, in take_action
  File "/usr/lib/python2.7/site-packages/kollacli/common/ansible/actions.py",line 89, in deploy
  File"/usr/lib/python2.7/site-packages/kollacli/common/ansible/playbook.py", line139, in run
    raise e
CommandError: ERROR: Command failed. :

The Docker Engine must be running on all target nodes before you deploy OpenStack. To resolve this issue:

  1. Remove the OpenStack services that are currently deployed on the target nodes.

    $ kollacli host destroy all
  2. Ensure that the Docker Engine is running on all target nodes.

    To check that the Docker Engine is running:

    $ systemctl status docker.service
    ● docker.service - Docker Application Container Engine
       Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/docker.service.d
               └─docker-sysconfig.conf, var-lib-docker-mount.conf
       Active: inactive (dead) since Tue 2016-03-29 13:20:53 BST; 2min 35s ago

    If the output of this command shows the status of the Docker service to be inactive (dead), start the Docker Engine:

    # systemctl start docker.service
  3. From the master node, deploy OpenStack services to the target nodes:

    $ kollacli deploy

Bug: 22979229