AWX Tower install failure (2 separate servers)
37 views
Skip to first unread message
John James
Nov 21, 2019, 9:48:17 AM11/21/19
to Ansible Project
Good Morning,
I am pretty new to Ansible, I had built an AWX Tower some months ago, but had to let it sit. Last week I started working on it again when that instance got stuck in an upgrade loop. I spent a few days trying to reinstall and in the end, I couldn't get passed a specific error. I decided to spin up a new VM server and do a fresh install. I ended up with the exact same error message.
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version: Timeout value connect was Timeout(connect=10, read=10, total=None), but it must be an int or float."
Is anyone familiar with this?
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version: Timeout value connect was Timeout(connect=10, read=10, total=None), but it must be an int or float."
Is anyone familiar with this?
Much thanks.
Stefan Hornburg (Racke)
Nov 21, 2019, 10:13:42 AM11/21/19
to ansible...@googlegroups.com
On 11/21/19 3:48 PM, John James wrote:
> Good Morning,
>
> I am pretty new to Ansible, I had built an AWX Tower some months ago, but had to let it sit. Last week I started
> working on it again when that instance got stuck in an upgrade loop. I spent a few days trying to reinstall and in the
> end, I couldn't get passed a specific error. I decided to spin up a new VM server and do a fresh install. I ended up
> with the exact same error message.
>
> *fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version:
> Good Morning,
>
> I am pretty new to Ansible, I had built an AWX Tower some months ago, but had to let it sit. Last week I started
> working on it again when that instance got stuck in an upgrade loop. I spent a few days trying to reinstall and in the
> end, I couldn't get passed a specific error. I decided to spin up a new VM server and do a fresh install. I ended up
> with the exact same error message.
>
> Timeout value connect was Timeout(connect=10, read=10, total=None), but it must be an int or float."
> *
> Is anyone familiar with this?
>
> Much thanks.
Please contact RedHat support. Neither tower nor AWX are a subject of this list.
>
> Much thanks.
Regards
Racke
>
> --
> 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
> ansible-proje...@googlegroups.com <mailto:ansible-proje...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/6d534ffb-2a2d-41f7-bc9f-a4779a245e22%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/6d534ffb-2a2d-41f7-bc9f-a4779a245e22%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
Bariou Alarou
Nov 21, 2019, 10:28:34 AM11/21/19
to ansible...@googlegroups.com
Hello John,
Update your /etc/yum.conf with bellow. The error is that API fetching is time out. This is not the best solution but it works form me when I was facing same problem.
--
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 ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6d534ffb-2a2d-41f7-bc9f-a4779a245e22%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages