Installing Ansible problem

27 views
Skip to first unread message

Botcherby, Peter

unread,
Jul 8, 2019, 1:10:58 PM7/8/19
to elasti...@googlegroups.com

Hi Riccardo,

 

I thought I would let elasticluster install ansible for me on the frontend but it has run into a problem

 

TASK [Mark host as successfully configured] *****************************************************************************************************

task path: /home/elasticluster/share/playbooks/main.yml:85

fatal: [frontend001]: UNREACHABLE! => {"changed": false, "msg": "Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: ( umask 77 && mkdir -p \"` echo /home/.ansible/tmp/ansible-tmp-1562604586.47-230724759639142 `\" && echo ansible-tmp-1562604586.47-230724759639142=\"` echo /home/.ansible/tmp/ansible-tmp-1562604586.47-230724759639142 `\" ), exited with result 127", "unreachable": true}

fatal: [compute001]: UNREACHABLE! => {"changed": false, "msg": "Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: ( umask 77 && mkdir -p \"` echo /home/.ansible/tmp/ansible-tmp-1562604586.5-260830003268834 `\" && echo ansible-tmp-1562604586.5-260830003268834=\"` echo /home/.ansible/tmp/ansible-tmp-1562604586.5-260830003268834 `\" ), exited with result 127", "unreachable": true}

 

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

 

PLAY RECAP **************************************************************************************************************************************

compute001                 : ok=103  changed=8    unreachable=1    failed=0    skipped=45   rescued=0    ignored=0

frontend001                : ok=150  changed=15   unreachable=1    failed=0    skipped=65   rescued=0    ignored=0

 

2019-07-08 16:49:46 a988e25d9acd gc3.elasticluster[1] ERROR Command `ansible-playbook --private-key=/home/pbotcherby/.ssh/SOE.key /home/elasticluster/share/playbooks/main.yml --inventory=/home/pbotcherby/.elasticluster/storage/rna2.inventory --become --become-user=root -vv -e @extra_vars.yml` failed with exit code 2.

2019-07-08 16:49:46 a988e25d9acd gc3.elasticluster[1] WARNING The cluster has likely *not* been configured correctly. You may need to re-run `elasticluster setup`.

2019-07-08 16:49:46 a988e25d9acd gc3.elasticluster[1] WARNING Cluster `rna2` not yet configured. Please, re-run `elasticluster setup rna2` and/or check your configuration

 

WARNING: YOUR CLUSTER `rna2` IS NOT READY YET!

 

 

Regards

Peter

 

ec-rna3.log

Riccardo Murri

unread,
Jul 8, 2019, 6:11:49 PM7/8/19
to Botcherby, Peter, elasti...@googlegroups.com
Hello Peter,

> fatal: [frontend001]: UNREACHABLE!

"nreachable" usually means that the SSH connection to the node was
severed (typically because of a network error). So, just trying again
later should solve the problem.

Anyway, in this particular case, the problem seems to have happened
during the very last task ("Mark hosts as successfully configured") so
the cluster should actually be crrectly configured already. I think
you can just ` elasticluster ssh` into it.

Ciao,
R
Reply all
Reply to author
Forward
0 new messages