cancel
Showing results for 
Search instead for 
Did you mean: 
fr4ncky
Cadet
Cadet
  • 612 Views

AWX/Ansible : timeout -1 when I try to call api

Hello,

We have an internal cloud throught a portal where we can launch backups, activate or deactivate a server monitoring etc.

=> When I use this portal to make this actions, I have no problem, it launch a job and it works.

=> When I use a VM of this portal to launch a Python3 or Python2 script to do backups, monitoring etc throught api call with request library, I don't have any problem too.(uri library)

=> But, when I launch my ansible playbook with api calls throught my playbook in AWX (server of this portail too), I have a "fatal: [serverxxx]: FAILED! => {"changed": false, "content": "", "elapsed": 90, "msg": "status code was -1 and not [200, 403]: connection failure: the read operation timed out", "redirected": false, "status": -1, "url": "httpsmyownworkcloud.en/api/v1/virtual_servers/serverxxx/snapshots/12334455"} with ansible.builtin.uri (timeout is defined by default to 30sec). When I increase this timeout in the playbook, sometimes the job does an timeout error -1. 

With my python script, timeout is not defined in the librairy (it's infinite) but it works every time and with no delay.

do you have any suggestion please or help?

Thanks for advance,

1 Reply
  • 596 Views

Could it be an issue with API call volume for the endpoint? I've seen ansible take down APIs when running with strategy: free on a large number of hosts.

Join the discussion
You must log in to join this conversation.