# "TypeError: update expected at most 1 arguments, got 2"

**URL:** <https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604>\
**Category:** AWX Project\
**Tags:** rhel, awx\
**Created:** [May 23, 2018, 6:13pm UTC](https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604 "2018-05-23T18:13:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dan\_linder](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dan_linder/32/3833_2.png) [@dan\_linder](https://forum.ansible.com/u/dan_linder)\
**Post date:** [May 23, 2018, 6:13pm UTC](https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604/1 "2018-05-23T18:13:36Z")

</div>

I’m running a simple playbook from within Ansible Tower but getting the error in the subject line.

Version info:

- Tower server: RHEL 7.5, Ansible 2.5.3, Ansible Tower 3.2.2
- Remote node: RHEL 7.5

The playbook has multiple hosts sections, all are defined like this (with line numbers):

> 21 - name: “Setup the testing TEST/DEV systems”  
> 22 hosts: test\_dev  
> …  
> 63 - name: “Setup the testing PPROD/PROD systems”  
> 64 hosts: test\_prod  
> …

> 103 - name: Setup of test systems

> 104 hosts: test\_sys

> 

The “test\_sys” group is just a collection of the “test\_dev” and “test\_prod” groups. The first two work just fine and gather facts, but the third errors out in the “Gathering Facts” step (lines truncated for length marked with ‘snip’):

> TASK [Gathering Facts] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
> task path: /var/lib/awx/projects/\_146\_\_ansibletowersetup/CICD-InfoSec-Testing/setuptesting.yml:103  
> Using module file /usr/lib/python2.7/site-packages/ansible/modules/system/setup.py  
> \<10.50.219.144\> ESTABLISH SSH CONNECTION FOR USER: root  
> \<10.50.219.144\> SSH: EXEC ssh -o UserKnownHostsFile=/dev/null -o ControlPersist=60s -o StrictHos […snip…]  
> Using module file /usr/lib/python2.7/site-packages/ansible/modules/system/setup.py  
> \<10.50.219.146\> ESTABLISH SSH CONNECTION FOR USER: root  
> \<10.50.219.146\> SSH: EXEC ssh -o UserKnownHostsFile=/dev/null -o ControlPersist=60s -o StrictHos […snip…]  
> \<10.50.219.144\> (0, '\n{“invocation”: {“module\_args”: {“filter”: “\*”, “gather\_subset”: [“all”], […snip…]  
> ERROR! Unexpected Exception, this is probably a bug: update expected at most 1 arguments, got 2  
> the full traceback was:
> 
> Traceback (most recent call last):  
> File “/usr/bin/ansible-playbook”, line 118, in   
> exit\_code = cli.run()  
> File “/usr/lib/python2.7/site-packages/ansible/cli/playbook.py”, line 122, in run  
> results = pbex.run()  
> File “/usr/lib/python2.7/site-packages/ansible/executor/playbook\_executor.py”, line 159, in run  
> result = self.\_tqm.run(play=play)  
> File “/usr/lib/python2.7/site-packages/ansible/executor/task\_queue\_manager.py”, line 289, in run  
> play\_return = strategy.run(iterator, play\_context)  
> File “/usr/lib/python2.7/site-packages/ansible/plugins/strategy/linear.py”, line 321, in run  
> results += self.\_wait\_on\_pending\_results(iterator)  
> File “/usr/lib/python2.7/site-packages/ansible/plugins/strategy/ **init**.py”, line 674, in \_wait\_on\_pending\_results  
> results = self.\_process\_pending\_results(iterator)  
> File “/usr/lib/python2.7/site-packages/ansible/plugins/strategy/ **init**.py”, line 117, in inner  
> results = func(self, iterator, one\_pass=one\_pass, max\_passes=max\_passes)  
> File “/usr/lib/python2.7/site-packages/ansible/plugins/strategy/ **init**.py”, line 606, in \_process\_pending\_results  
> self.\_variable\_manager.set\_host\_facts(target\_host, result\_item[‘ansible\_facts’].copy())  
> File “/usr/lib/python2.7/site-packages/ansible/vars/manager.py”, line 587, in set\_host\_facts  
> self.\_fact\_cache.update(host.name, facts)  
> TypeError: update expected at most 1 arguments, got 2

Any ideas where to start looking?

---

<div class="post-metadata">

**Author:** ![rpetrell](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rpetrell](https://forum.ansible.com/u/rpetrell)\
**Post date:** [May 23, 2018, 6:39pm UTC](https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604/2 "2018-05-23T18:39:58Z")

</div>

Dan,

This looks to me like a bug in Ansible _itself_, rather than awx.

---

<div class="post-metadata">

**Author:** ![rpetrell](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rpetrell](https://forum.ansible.com/u/rpetrell)\
**Post date:** [May 23, 2018, 6:45pm UTC](https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604/3 "2018-05-23T18:45:19Z")

</div>

Dan,

For help with Ansible, you might try the Ansible mailing list:[https://groups.google.com/forum/#!forum/ansible-project](https://groups.google.com/forum/#!forum/ansible-project)

Or the Ansible IRC room on freenode (#ansible)

Based on your usage of Ansible Tower, you might also consider reaching out to your account representative at Red Hat (this mailing list is specifically for the open source awx project).

---

<div class="post-metadata">

**Author:** ![dan\_linder](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dan_linder/32/3833_2.png) [@dan\_linder](https://forum.ansible.com/u/dan_linder)\
**Post date:** [May 23, 2018, 7:36pm UTC](https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604/4 "2018-05-23T19:36:15Z")

</div>

I’d agree, but when I run the playbook from the command line that error doesn’t come up so I’m suspecting something with the AnsibleTower-AnsibleCore interactions.

---

<div class="post-metadata">

**Author:** ![dan\_linder](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dan_linder/32/3833_2.png) [@dan\_linder](https://forum.ansible.com/u/dan_linder)\
**Post date:** [May 23, 2018, 7:36pm UTC](https://forum.ansible.com/t/typeerror-update-expected-at-most-1-arguments-got-2/27604/5 "2018-05-23T19:36:56Z")

</div>

I’ll open a ticket with RedHat support to see what they say.
