before my issue I was missing connection: local now I am able to run and I 
am getting message below I have doubled checked my username and password 
below is my .yaml syntax

TASK [show version] 
***************************************************************************************************************************************************

fatal: [vegetacore01_temp]: FAILED! => {"msg": "Invalid/incorrect 
username/password. Private key file is encrypted"}

fatal: [vegetacore02_temp]: FAILED! => {"msg": "Invalid/incorrect 
username/password. Private key file is encrypted"}

 

---

- name: INE_NXOS

  hosts: sjc_core

  connection: local

 

 

  vars:

    cli:

      host: "{{ inventory_hostname }}"

      username: vegeta

      password: abc123

      transport: cli

 

  tasks:

    - name: show version

      nxos_command:

        commands: show version

        provivder: "{{ cli }}"





On Monday, February 25, 2019 at 1:31:32 PM UTC-5, VeGeTa-X wrote:
>
> ok fixed my issue I was missing "connection:local" in my playbook thx for 
> your help
>
> On Monday, February 25, 2019 at 1:05:33 PM UTC-5, VeGeTa-X wrote:
>>
>> when I do a  ansible all -i inventory/inv_sjc_core -u vegeta -m ping -k 
>> it does not authenticate but if I do a "ssh -l vegeta vegeta01_temp" it 
>> works
>>
>>
>> vegeta01_temp | 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 Cmd 
>> exec error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" 
>> && echo ansible-tmp-1551117540.2506652-80180766644234=\"` echo Cmd exec 
>> error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" ), 
>> exited with result 16, stdout output: Syntax error while parsing '/bin/sh 
>> -c '( umask 77 && mkdir -p \"` echo Cmd exec 
>> error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" && 
>> echo ansible-tmp-1551117540.2506652-80180766644234=\"` echo Cmd exec 
>> error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" ) && 
>> sleep 0''\n\n\nCmd exec error.\n",
>>
>>     "unreachable": true
>>
>> }
>>
>> vegeta02_temp | 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 Cmd 
>> exec error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" 
>> && echo ansible-tmp-1551117540.287293-48560425026336=\"` echo Cmd exec 
>> error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" ), 
>> exited with result 16, stdout output: Syntax error while parsing '/bin/sh 
>> -c '( umask 77 && mkdir -p \"` echo Cmd exec 
>> error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" && 
>> echo ansible-tmp-1551117540.287293-48560425026336=\"` echo Cmd exec 
>> error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" ) && 
>> sleep 0''\n\n\nCmd exec error.\n",
>>
>>     "unreachable": true
>>
>> }
>>
>> [root@ansiblevm ansible]#
>>
>>
>>
>>
>>
>>
>> On Sunday, February 24, 2019 at 2:22:49 PM UTC-5, d...@linder.org wrote:
>>>
>>> On Saturday, February 23, 2019 at 5:11:45 PM UTC-6, VeGeTa-X wrote:
>>>>
>>>> ok fixed the username and password and I am still not able to login 
>>>> using the playbook
>>>>
>>>
>>> Please provide the new error message you're getting.  Can you do a 
>>> simple "ansible ping" (
>>> https://docs.ansible.com/ansible/latest/user_guide/intro_getting_started.html#your-first-commands
>>> ).
>>>
>>> Dan
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/57ddda1a-55cd-4a2b-a950-717f228a30a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to