Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in "/tmp". Failed command was: mk

2,741 views
Skip to first unread message

rrrki...@gmail.com

unread,
Apr 21, 2015, 9:14:02 AM4/21/15
to ansible...@googlegroups.com
I am getting this error when I ran the playbook for the remote node .

Could you please let me know how to resolve this error ?

Yassen Damyanov

unread,
Apr 23, 2015, 3:15:04 PM4/23/15
to ansible...@googlegroups.com

On Tuesday, April 21, 2015 at 4:14:02 PM UTC+3, rrrki...@gmail.com wrote:
I am getting this error when I ran the playbook for the remote node .

Could you please let me know how to resolve this error ?


1. Quoting from openbsd netiquette: "No one other than you has the information needed to resolve your problem, it is better to provide more information than needed than one detail too little".
Ideas:
-- Provide your task or playbook code that spits out this error;
-- Run the command with -vvvv for maximum verbosity and check the output. If it does not speak much to you, provide it here to the list for help.

2. Please use short (but descriptive) subjects for your messages. By no means paste a long error message like that as a subject. (It seems truncated, btw.)

(And yes, your name as a signature will help people recognize you, which seems helpful.)

BR,
Yassen

Laurent Hory

unread,
Feb 4, 2016, 12:37:23 PM2/4/16
to Ansible Project
Hi,

I have a same issue.

Version:
ansible --version                                                                                                                                                   16:21:55  ✔ 0
/usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
ansible 2.0.0.2
  config file =
  configured module search path = Default w/o overrides


Command line
$ ansible-playbook -i hosts playbook.yml -vvv
/usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
Using /home_raid1/laurent/dev/AIA/ansible.cfg as config file
1 plays in playbook.yml

PLAY [create aia user] *********************************************************

TASK [setup] *******************************************************************
<3.249.12.53> ESTABLISH SSH CONNECTION FOR USER: root
<3.249.12.53> SSH: EXEC ssh -C -q -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=/home_raid1/laurent/.ansible/cp/ansible-ssh-%h-%p-%r -tt 3.249.12.53 'mkdir -p "$( echo /tmp/ansible/$USER/ansible-tmp-1454599171.43-1430744300902 )" && echo "$( echo /tmp/ansible/$USER/ansible-tmp-1454599171.43-1430744300902 )"'
fatal: [rubis]: UNREACHABLE! => {"changed": false, "msg": "ERROR! Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: mkdir -p \"$( echo /tmp/ansible/$USER/ansible-tmp-1454599171.43-1430744300902 )\" && echo \"$( echo /tmp/ansible/$USER/ansible-tmp-1454599171.43-1430744300902 )\", exited with result 1: Illegal variable name.\r\n", "unreachable": true}

PLAY RECAP *********************************************************************
rubis                      : ok=0    changed=0    unreachable=1    failed=0


Playbook:
- name: "create aia user"
  hosts: "rubis"
  user: "root"
  roles:
    - user

Role:
- name: create {{new_user}} user
  user:
    name: "{{new_user}}"
    password: "{{ password }}"
    comment: "specific aia user"
    group: "awuser"
    shell: "/bin/tcsh"
    groups: "awuser,iaa-v3d,sdc"
    append: "yes"
    state: "present"

- name: add cshrc files
  template: src=.AWArc
            dest=/home/{{new_user}}/.AWArc
  template: src=.cshrc
            dest=/home/{{new_user}}/.cshrc
  template: src=.cshrc.atria
            dest=/home/{{new_user}}/.cshrc.atria



Thanks

Laurent Hory

unread,
Feb 12, 2016, 9:17:57 AM2/12/16
to Ansible Project
On my workstation this issue is only with ansible 2.0.2.
ansible 1.9.4 work

Timothy Vandenbrande

unread,
Feb 22, 2016, 8:57:25 AM2/22/16
to Ansible Project
I can confirm this.
I have this issue on ansible 2.0.0.2, but works on ansible 1.9.x
I get this error whicle running a script on a windows host.

In playbook:
- name: set some default settings
  script: defaults.ps1


In output:
fatal: [acc-rt1903-sta]: UNREACHABLE! => {"changed": false, "msg": "ERROR! Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: PowerShell -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -EncodedCommand UwBlAHQALQBTAHQAcgBpAGMAdABNAG8AZABlACAALQBWAGUAcgBzAGkAbwBuACAATABhAHQAZQBzAHQACgAoAE4AZQB3AC0ASQB0AGUAbQAgAC0AVAB5AHAAZQAgAEQAaQByAGUAYwB0AG8AcgB5ACAALQBQAGEAdABoACAAJABlAG4AdgA6AHQAZQBtAHAAIAAtAE4AYQBtAGUAIAAiAGEAbgBzAGkAYgBsAGUALQB0AG0AcAAtADEANAA1ADYAMQA0ADgAOAA1ADAALgAyADMALQAxADQAMgA0ADcAOAA0ADQAOAA1ADMANwA4ADEANAAiACkALgBGAHUAbABsAE4AYQBtAGUAIAB8ACAAVwByAGkAdABlAC0ASABvAHMAdAAgAC0AUwBlAHAAYQByAGEAdABvAHIAIAAnACcAOwA=, exited with result 1", "unreachable": true}

J Hawkesworth

unread,
Feb 22, 2016, 10:23:14 AM2/22/16
to Ansible Project
Hi,

Can I check that you have replaced your ansible.cfg with a new version supplied with ansible 2.0.0.2?

Jon
Reply all
Reply to author
Forward
0 new messages