The issue is fixed by PR #49174 and the fix is available in Ansible version
2.7.5
Please retest with 2.7.5 version and check if the issue is still seen.
Regards,
Ganesh
On Saturday, 12 January 2019 06:01:40 UTC+5:30, Mike Dodd wrote:
>
> 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
>
>
> -------
> -Failure:
>
> The full traceback is:
>
> Traceback (most recent call last):
>
> File "/usr/local/bin/ansible-connection", line 290, in main
>
> messages.extend(conn.update_play_context(pc_data))
>
> File
> "/usr/local/lib/python2.7/site-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: [infr-rt002-d06.nae02.use1.viasat.cloud]: FAILED! => {
>
> "msg": "'Connection' object has no attribute 'reset_history'"
>
> }
>
>
>
> On Friday, October 12, 2018 at 9:26:04 AM UTC-7, DC wrote:
>>
>> 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
>>
>
--
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/12de3660-6cac-4ed1-a82f-cb72bf4180e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
