<zarkon.dc3.crunchtools.com> (0, '', '')
<zarkon.dc3.crunchtools.com> ESTABLISH SSH CONNECTION FOR USER: root
<zarkon.dc3.crunchtools.com> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/a20b58642e -tt zarkon.dc3.crunchtools.com '/bin/sh -c '"'"'/usr/bin/python /root/.ansible/tmp/ansible-tmp-1523146405.87-11948946632593/systemd.py; rm -rf "/root/.ansible/tmp/ansible-tmp-1523146405.87-11948946632593/" > /dev/null 2>&1 && sleep 0'"'"''
<zarkon.dc3.crunchtools.com> (0, '\r\n{"msg": "Unable to restart service atomic-openshift-node: Job for atomic-openshift-node.service failed because the control process exited with error code. See \\"systemctl status atomic-openshift-node.service\\" and \\"journalctl -xe\\" for details.\\n", "failed": true, "invocation": {"module_args": {"no_block": false, "name": "atomic-openshift-node", "enabled": null, "daemon_reload": false, "state": "restarted", "user": false, "masked": null}}}\r\n', 'Shared connection to zarkon.dc3.crunchtools.com closed.\r\n')
fatal: [zarkon.dc3.crunchtools.com]: FAILED! => {
    "attempts": 3,
    "changed": false,
    "invocation": {
        "module_args": {
            "daemon_reload": false,
            "enabled": null,
            "masked": null,
            "name": "atomic-openshift-node",
            "no_block": false,
            "state": "restarted",
            "user": false
        }
    },
    "msg": "Unable to restart service atomic-openshift-node: Job for atomic-openshift-node.service failed because the control process exited with error code. See \"systemctl status atomic-openshift-node.service\" and \"journalctl -xe\" for details.\n"
}

RUNNING HANDLER [openshift_node : reload systemd units] ********************************************************
META: ran handlers
	to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.retry

PLAY RECAP *****************************************************************************************************
allura.dc3.crunchtools.com : ok=45   changed=9    unreachable=0    failed=0
coran.dc3.crunchtools.com  : ok=426  changed=150  unreachable=0    failed=1
hunk.dc3.crunchtools.com   : ok=307  changed=114  unreachable=0    failed=1
localhost                  : ok=14   changed=0    unreachable=0    failed=0
pidge.dc3.crunchtools.com  : ok=307  changed=114  unreachable=0    failed=1
sven.dc3.crunchtools.com   : ok=107  changed=33   unreachable=0    failed=1
yurak.dc3.crunchtools.com  : ok=107  changed=33   unreachable=0    failed=1
zarkon.dc3.crunchtools.com : ok=107  changed=33   unreachable=0    failed=1


INSTALLER STATUS ***********************************************************************************************
Initialization             : Complete (0:01:11)
Health Check               : Complete (0:02:44)
etcd Install               : Complete (0:07:46)
NFS Install                : Complete (0:00:48)
Load balancer Install      : Complete (0:02:08)
Master Install             : Complete (0:15:08)
Master Additional Install  : Complete (0:10:26)
Node Install               : In Progress (0:22:38)
	This phase can be restarted by running: playbooks/openshift-node/config.yml



Failure summary:


  1. Hosts:    coran.dc3.crunchtools.com, hunk.dc3.crunchtools.com, pidge.dc3.crunchtools.com, sven.dc3.crunchtools.com, yurak.dc3.crunchtools.com, zarkon.dc3.crunchtools.com
     Play:     Configure nodes
     Task:     restart node
     Message:  Unable to restart service atomic-openshift-node: Job for atomic-openshift-node.service failed because the control process exited with error code. See "systemctl status atomic-openshift-node.service" and "journalctl -xe" for details.