# Until is giving issues with ansible 2.1

**URL:** <https://forum.ansible.com/t/until-is-giving-issues-with-ansible-2-1/22509>\
**Category:** Ansible Project\
**Created:** [September 8, 2016, 11:17am UTC](https://forum.ansible.com/t/until-is-giving-issues-with-ansible-2-1/22509 "2016-09-08T11:17:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deepa\_Yr](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@Deepa\_Yr](https://forum.ansible.com/u/Deepa_Yr)\
**Post date:** [September 8, 2016, 11:17am UTC](https://forum.ansible.com/t/until-is-giving-issues-with-ansible-2-1/22509/1 "2016-09-08T11:17:28Z")

</div>

Hi

Earlier we were using Ansible 2.0.1 where playbooks were running fine. Now upgraded to Ansible 2.1.1. Seeing issues with until module.

- name: Copy the file  
get\_url:  
headers: “{{ headers }}”  
url: “{{ asset\_repo\_url }}/{{ file\_path }}”  
dest: “{{ file\_dest }}”  
checksum: md5:{{ file\_md5 }}  
register: get\_url\_result  
until: “‘OK’ in get\_url\_result.msg or ‘file already exists’ in get\_url\_result.msg”  
ignore\_errors: true

In this if until command is commented, then it runs fine. Can you please let me know how it should be used in Ansible 2.1.1 version.  
Many thanks

Regards  
Deepa

---

<div class="post-metadata">

**Author:** ![Deepa\_Yr](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@Deepa\_Yr](https://forum.ansible.com/u/Deepa_Yr)\
**Post date:** [September 8, 2016, 11:18am UTC](https://forum.ansible.com/t/until-is-giving-issues-with-ansible-2-1/22509/2 "2016-09-08T11:18:43Z")

</div>

This is the error noticed

An exception occurred during task execution. The full traceback is:  
Traceback (most recent call last):  
File “/usr/lib/python2.7/site-packages/ansible/executor/task\_executor.py”, line 124, in run  
res = self.\_execute()  
File “/usr/lib/python2.7/site-packages/ansible/executor/task\_executor.py”, line 427, in \_execute  
retries = self.\_task.retries + 1  
TypeError: unsupported operand type(s) for +: ‘NoneType’ and ‘int’  
fatal: [localhost]: FAILED! =\> {“failed”: true, “msg”: “Unexpected failure during module execution.”, “stdout”: “”}