# sros network modules in ansible 2.7.0

**URL:** <https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [October 12, 2018, 4:26pm UTC](https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777 "2018-10-12T16:26:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DC11](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@DC11](https://forum.ansible.com/u/DC11)\
**Post date:** [October 12, 2018, 4:26pm UTC](https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777/1 "2018-10-12T16:26:04Z")

</div>

Ansible newbie here. I’m trying to learn about network\_cli so installed a recent version of ansible

`

ansible --version  
ansible 2.7.0  
config file = /etc/ansible/ansible.cfg  
configured module search path = [u’/home/ubuntu/.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  
python version = 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0]

`

It appears the first task/commands executes ok, but as soon as I add a second task in the playbook (even a debug task) I end up with the error:

`

TASK [sros\_command] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
task path: /tmp/sros.yml:7  
The full traceback is:  
Traceback (most recent call last):  
File “/usr/bin/ansible-connection”, line 290, in main  
messages.extend(conn.update\_play\_context(pc\_data))  
File “/usr/lib/python2.7/dist-packages/ansible/module\_utils/connection.py”, line 173, in **rpc**  
raise ConnectionError(to\_text(msg, errors=‘surrogate\_then\_replace’), code=code)  
ConnectionError: ‘Connection’ object has no attribute ‘reset\_history’

fatal: [sr]: FAILED! =\> {  
“msg”: “‘Connection’ object has no attribute ‘reset\_history’”  
}

`

Even trying to revert back to using ‘provider’ and ‘connection: local’ fails with a similar error.

Thanks,  
DC

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [October 19, 2018, 1:26pm UTC](https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777/2 "2018-10-19T13:26:18Z")

</div>

Hi,  
Could you please raise a bug at [https://github.com/ansible/ansible/issues/new/choose](https://github.com/ansible/ansible/issues/new/choose) and include the two tasks (and any group\_vars/inventory, etc)

Kind regards,  
gundalow

---

<div class="post-metadata">

**Author:** ![Mike\_Dodd](https://avatars.discourse-cdn.com/v4/letter/m/dc4da7/32.png) [@Mike\_Dodd](https://forum.ansible.com/u/Mike_Dodd)\
**Post date:** [January 12, 2019, 12:31am UTC](https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777/3 "2019-01-12T00:31:40Z")

</div>

Here is a perfect example of the bug, also using Ansible 2.7.0:

- name: TWO TASKS BREAKS SROS  
hosts: sros  
connection: local  
gather\_facts: no

vars\_files:

- group\_vars/all

tasks:

- name: Get Router system name  
sros\_command:  
provider: “{{ router\_auth }}”  
commands: show system information | match “System Name”  
register: system\_name

- debug:  
var: system\_name

- name: Configure VPLS service  
sros\_config:  
provider: “{{ router\_auth }}”  
parents:

- configure service

- vpls “{{ internet\_vpls\_id }}” customer 1 create

- allow-ip-int-bind  
lines: exit  
register: vpls

- debug:  
var: vpls

---

<div class="post-metadata">

**Author:** ![ganeshrn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ganeshrn/32/1021_2.png) [@ganeshrn](https://forum.ansible.com/u/ganeshrn)\
**Post date:** [January 12, 2019, 8:20am UTC](https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777/4 "2019-01-12T08:20:25Z")

</div>

The issue is fixed by PR #49174 and the fix is available in Ansible version 2.7.5Please retest with 2.7.5 version and check if the issue is still seen.

Regards,  
Ganesh

---

<div class="post-metadata">

**Author:** ![Stan\_Kozlov](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@Stan\_Kozlov](https://forum.ansible.com/u/Stan_Kozlov)\
**Post date:** [March 22, 2019, 1:32pm UTC](https://forum.ansible.com/t/sros-network-modules-in-ansible-2-7-0/28777/5 "2019-03-22T13:32:47Z")

</div>

I has similar issue with 7750 TiMOS-C-14.0.R5 and Ansible 2.7.0  
Upgrade up to 2.7.5 has fixed the issue

Cheers