Thanks for the additional details.  Its definitely a bug that affects the 
9K (the nxapi implementation is a little different).  Working on a fix that 
will be available soon

On Monday, March 7, 2016 at 5:44:45 PM UTC-5, Roger Gomez wrote:
>
>
>
> On Sunday, March 6, 2016 at 10:43:54 PM UTC-5, [email protected] wrote:
>>
>> HI Roger,
>>
>> Two questions:
>>
>> 1) Are you able to browse to http://leaf-switch:80/ins 
>> <http://leaf-switch/ins> (assuming you have nxapi sandbox configured)?
>>
>     Yes, I'm able to browse and make REST API calls.  
>
>>
>> 2) What platform and nxos version are you running?
>>
>    This test was in n9000-dk9.*7.0.3.I1.2*.bin but I also did it in 
> on 6.1(2)I3(1) 
>
>>
>>
>>
>> On Friday, March 4, 2016 at 6:52:37 PM UTC-5, Roger Gomez wrote:
>>>
>>> I have been trying to test the Cisco NXOS modules and the nxos_command 
>>> is failing and I don't understand why:
>>> cmd.yml
>>> ---
>>> - hosts:
>>>   - leaf-switch
>>>   gather_facts: no
>>>   tasks:
>>>   - nxos_command:
>>>      username: user
>>>      password: password
>>>      commands:
>>>      - show version
>>>      transport: nxapi
>>>      use_ssl: no
>>>      host: leaf-switch
>>>     delegate_to: localhost
>>>
>>> When I run the playbook I have this back:
>>>
>>>> PLAY 
>>>>> ***************************************************************************
>>>>
>>>>
>>>>> TASK [nxos_command] 
>>>>> ************************************************************
>>>>
>>>> fatal: [leaf-switch -> localhost]: FAILED! => {"changed": false, 
>>>>> "failed": true, "msg": "HTTP Error 400: Bad Request", "status": 400, 
>>>>> "url": 
>>>>> "http://leaf-switch:80/ins"}
>>>>
>>>>
>>>>> NO MORE HOSTS LEFT 
>>>>> *************************************************************
>>>>
>>>> to retry, use: --limit @com.retry
>>>>
>>>>
>>>>> PLAY RECAP 
>>>>> *********************************************************************
>>>>
>>>> leaf-switch                : ok=0    changed=0    unreachable=0    
>>>>> failed=1
>>>>
>>>>
>>>> The switch is enable for NXAPI and I can use it, if I only change the 
>>> transport from nxapi to cli everything works just fine.
>>> Any idea what could be the reason?
>>> Thanks. 
>>>  
>>>
>>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/ae44fd00-2ff0-4e94-8788-70927460e2eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to