# Unable to setup AWX (1.0.3.5) using the kubernetes deployment process.

**URL:** <https://forum.ansible.com/t/unable-to-setup-awx-1-0-3-5-using-the-kubernetes-deployment-process/26653>\
**Category:** AWX Project\
**Tags:** kubernetes, fedora, awx\
**Created:** [February 3, 2018, 4:51pm UTC](https://forum.ansible.com/t/unable-to-setup-awx-1-0-3-5-using-the-kubernetes-deployment-process/26653 "2018-02-03T16:51:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cesar\_Sanchez2](https://avatars.discourse-cdn.com/v4/letter/c/f6c823/32.png) [@Cesar\_Sanchez2](https://forum.ansible.com/u/Cesar_Sanchez2)\
**Post date:** [February 3, 2018, 4:51pm UTC](https://forum.ansible.com/t/unable-to-setup-awx-1-0-3-5-using-the-kubernetes-deployment-process/26653/1 "2018-02-03T16:51:14Z")

</div>

Hello guys.

I’ve setup a kubernetes cluster, and I’m trying to deploy the awx project pods.

Everything seems to work, but…then, accessing the external endpoint I set for the service, the server displays the AWX migrating page and hangs there, forever…

I checked the awx\_web container errors and this is what displays:

“[http://10.10.150.10/migrations\_notran/](http://10.10.150.10/migrations_notran/)” “Mozilla/5.0 (X11; Fedora; Linux x86\_64; rv:58.0) Gecko/20100101 Firefox/58.0” “-”  
2018-02-03 16:41:35,870 ERROR Error trying to receive messages: ‘thread.\_local’ object has no attribute ‘consumer’  
2018-02-03 16:41:40,871 ERROR Error trying to receive messages: ‘thread.\_local’ object has no attribute ‘consumer’  
2018/02/03 16:41:43 [error] 41#0: \*1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.27.74, server: \_, request: “GET / HTTP/1.1”, upstream: “uwsgi://[::1]:8050”, host: “10.10.150.10”, referrer:

The awx\_celery container:  
[2018-02-03 16:47:10,032: DEBUG/Beat] beat: Waking up in 10.00 seconds.  
[2018-02-03 16:47:18,664: DEBUG/MainProcess] heartbeat\_tick : for connection 9ded4952d28545499d38a32dfa0af6ef  
[2018-02-03 16:47:18,664: DEBUG/MainProcess] heartbeat\_tick : Prev sent/recv: 36/1048, now - 36/1078, monotonic - 578537.802219, last\_heartbeat\_sent - 578497.798695, heartbeat int. - 60 for connection 9ded4952d28545499d38a32dfa0af6ef  
[2018-02-03 16:47:20,039: INFO/Beat] Scheduler: Sending due task task\_manager (awx.main.scheduler.tasks.run\_task\_manager)  
[2018-02-03 16:47:20,041: DEBUG/Beat] awx.main.scheduler.tasks.run\_task\_manager sent. id-\>07587517-4f18-4a02-8199-a8e0d20235b4  
[2018-02-03 16:47:20,041: DEBUG/Beat] beat: Waking up in 19.99 seconds.  
[2018-02-03 16:47:38,665: DEBUG/MainProcess] heartbeat\_tick : for connection 9ded4952d28545499d38a32dfa0af6ef  
[2018-02-03 16:47:38,665: DEBUG/MainProcess] heartbeat\_tick : Prev sent/recv: 36/1078, now - 36/1108, monotonic - 578557.802595, last\_heartbeat\_sent - 578497.798695, heartbeat int. - 60 for connection 9ded4952d28545499d38a32dfa0af6ef  
[2018-02-03 16:47:38,665: DEBUG/MainProcess] heartbeat\_tick: sending heartbeat for connection 9ded4952d28545499d38a32dfa0af6ef  
[2018-02-03 16:47:40,049: INFO/Beat] Scheduler: Sending due task task\_manager (awx.main.scheduler.tasks.run\_task\_manager)  
[2018-02-03 16:47:40,051: DEBUG/Beat] awx.main.scheduler.tasks.run\_task\_manager sent. id-\>7b2682f3-e77d-4479-b3cb-568e23ce51a9  
[2018-02-03 16:47:40,051: INFO/Beat] Scheduler: Sending due task tower\_scheduler (awx.main.tasks.awx\_periodic\_scheduler)  
[2018-02-03 16:47:40,053: DEBUG/Beat] awx.main.tasks.awx\_periodic\_scheduler sent. id-\>c019998e-1041-4b0e-a6ea-c265b1553617  
[2018-02-03 16:47:40,053: INFO/Beat] Scheduler: Sending due task cluster\_heartbeat (awx.main.tasks.cluster\_node\_heartbeat)  
[2018-02-03 16:47:40,055: DEBUG/Beat] awx.main.tasks.cluster\_node\_heartbeat sent. id-\>3403105d-2428-424b-bf2c-16cada6bff2a  
[2018-02-03 16:47:40,055: DEBUG/Beat] beat: Waking up in 19.98 seconds.

awx\_rabbit:  
=INFO REPORT==== 3-Feb-2018::16:35:59 ===  
connection \<0.823.0\> (127.0.0.1:44678 -\> 127.0.0.1:5672): user ‘awx’ authenticated and granted access to vhost ‘awx’

This kinda happens a lot, the migration being stuck, I’d like to know how to resolve that issue.

It usually happens to us, in our current docker installed setup, whenever we want to upgrade to certain releases, it’s the same.

Thanks for your help.

-Cesar