Installed AWX but unable to login using default admin and password

Archives AWX Project
1

So I’m really new to this and I’ve spent soo much time trying to install AWX. I follow the AWX install guide on Github to the best of my ability but for some reason the default admin and password (in the inventory file) isn’t working when I try login in the webUi.

I’m also unable to change the password (on the initial install by editing the inventory file)
the same user and password works when I access rest API.

There appears to be a key component that’s lacking in my setup but due to my lack of exposure to this application I haven’t been able to determine the root cause. Any help would be appreciated.

Thanks.

2

How are you installing AWX? In any case, if you can get into one of the containers, you can run “awx-manage createsuperuser”. Does that help?

3

I followed this document -

https://github.com/ansible/awx/blob/devel/INSTALL.md#docker-or-docker-compose

Additionally, How do I access the container? I’ve tried creating a user using different methods - ex. both python manage.py createsuperuser - I don’t get new password prompt. just go back to linux prompt.

4

I may have to run another install on a clean Ubuntu setup.

I noticed that executables were stored in the /home/user/ Directory instead of usr/bin/

Not quite sure where I went wrong but I'm gonna chalk it up to me just being a noob.

5

I copied both awx-manage and awx-python to use/local/bin but now I’m getting

Pkg_resources.distributionnotfound: The ‘awx’ distribution was not found and is needed for this application.

6

So after much digging I've been able to make some progress.

So awx containers are managed by Kubernets (I have limited access) so through the portal I was able to manage the pods just fine using the exec feature. I created new users, updated passwords but still couldn't login.

I finally figured out how to bypass Kubernetes and access the web application and Bam...it worked. So I'm not sure if anyone can give me any other pointers but I'm betting this is a Kubernetes/loadbalancer issue.

Anyways just thought I'd share my findings just in case anyone has the same issue.