Hi there,
I am working on eos_ switches but when I am trying to get device running
configuration, instead of the device running-config I am getting following
error. I there any bug in 2.5 for Eos modules.
fatal: [192.68.122.115]: FAILED! => {"msg": "timed out"}
Similarly, I am trying with ansible 2.4.3 still am getting following error
root@tower:/home/ubuntu/NetworkAutomation/Network# ansible-playbook
eos_test1.yaml -vvvv
ansible-playbook 2.4.3.0
config file = /home/ubuntu/NetworkAutomation/Network/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules',
u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible-playbook
python version = 2.7.6 (default, Nov 23 2017, 15:49:48) [GCC 4.8.4]
Using /home/ubuntu/NetworkAutomation/Network/ansible.cfg as config file
setting up inventory plugins
Parsed /home/ubuntu/NetworkAutomation/Network/hosts inventory source with
ini plugin
Loading callback plugin default of type stdout, v2.0 from
/usr/lib/python2.7/dist-packages/ansible/plugins/callback/default.pyc
PLAYBOOK: eos_test1.yaml
********************************************************************************************************************************************************************
1 plays in eos_test1.yaml
PLAY [EOS Show Commands]
********************************************************************************************************************************************************************
META: ran handlers
TASK [eos show commands]
********************************************************************************************************************************************************************
task path: /home/ubuntu/NetworkAutomation/Network/eos_test1.yaml:16
<192.168.122.115> connection transport is cli
<192.168.122.115> using connection plugin network_cli
<192.168.122.115> socket_path: None
fatal: [192.168.122.115]: FAILED! => {
"changed": false,
"msg": "unable to open shell. Please see:
https://docs.ansible.com/ansible/network_debug_troubleshooting.html#unable-to-open-shell";
}
PLAY RECAP
**********************************************************************************************************************************************************************************
192.168.122.115 : ok=0 changed=0 unreachable=0 failed=1
Any lead is highly appreciated.
sample playbook
---
- name: EOS Show Commands
hosts: eos
gather_facts: false
connection: local
vars:
cli:
host: "{{ ansible_host }}"
username: "admin"
password: "admin"
authorize: true
transport: cli
tasks:
- name: eos show commands
eos_command:
commands:
- show version
provider: "{{ cli }}"
register: output
- name: show output
debug:
var: output
- name: vlan
eos_vlan:
vlan_id: 4000
name: vlan-4000
state: present
provider: "{{cli}}"
Thanks,
Shubham
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
