After deploy, ui login does not work

Archives AWX Project
, ,
1

After I deploy awx using minikube I am unable to log into the UI.

I checked selinux, verifying the user exists etc… I still get “There was a problem signing in. Please try again.”. I think the admin account exists, at least it tells me it does.

I run this and get the password:
minikube kubectl – get secret awx-admin-password -o jsonpath=‘{.data.password}’ | base64 --decode

I tried to create superuser just in case but it states super user admin already exists, so I created another dummy account and that still doesn’t work. Hey at least the web page looks shiny :).
This is a RHeL 8.3 server

Below is a bit of what I did to deploy.

wget https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm
–2021-05-25 17:45:40-- https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm
Resolving github.com (github.com)… 140.82.112.3
Connecting to github.com (github.com)|140.82.112.3|:443… connected.
HTTP request sent, awaiting response… 302 Found
Location: https://github-releases.githubusercontent.com/56353740/d7369b80-7ce4-11eb-9690-bbd4b776a344?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210525%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210525T214541Z&X-Amz-Expires=300&X-Amz-Signature=583793329787419a56b29eba3d16cfec4164d2a294ac4b26ffa153d21c9d768e&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=56353740&response-content-disposition=attachment%3B%20filename%3Dminikube-1.18.1-0.x86_64.rpm&response-content-type=application%2Foctet-stream [following]
–2021-05-25 17:45:41-- https://github-releases.githubusercontent.com/56353740/d7369b80-7ce4-11eb-9690-bbd4b776a344?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210525%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210525T214541Z&X-Amz-Expires=300&X-Amz-Signature=583793329787419a56b29eba3d16cfec4164d2a294ac4b26ffa153d21c9d768e&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=56353740&response-content-disposition=attachment%3B%20filename%3Dminikube-1.18.1-0.x86_64.rpm&response-content-type=application%2Foctet-stream
Resolving github-releases.githubusercontent.com (github-releases.githubusercontent.com)… 185.199.108.154, 185.199.109.154, 185.199.110.154, …
Connecting to github-releases.githubusercontent.com (github-releases.githubusercontent.com)|185.199.108.154|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 14329512 (14M) [application/octet-stream]
Saving to: ‘minikube-1.18.1-0.x86_64.rpm’

minikube-1.18.1-0.x86_64.rpm 100%[========================================================================================================================================>] 13.67M 10.4MB/s in 1.3s

[null@server01 awx]$ sudo rpm -Uvh minikube-1.18.1-0.x86_64.rpm
[null@server01 awx]$ minikube start --driver=podman --container-runtime=cri-o --cpus=4 --memory=8g --addons=ingress

! Your cgroup does not allow setting memory.

  • Starting control plane node minikube in cluster minikube
  • Downloading Kubernetes v1.20.2 preload …

preloaded-images-k8s-v9-v1…: 560.29 MiB / 560.29 MiB 100.00% 6.62 MiB

  • Creating podman container (CPUs=4, Memory=8192MB) …
  • Preparing Kubernetes v1.20.2 on CRI-O 1.20.0 …
  • Generating certificates and keys …
  • Booting up control plane …
  • Configuring RBAC rules …
  • Configuring CNI (Container Networking Interface) …
  • Verifying Kubernetes components…

kubectl.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s
kubectl: 38.37 MiB / 38.37 MiB [---------------] 100.00% 1.37 MiB p/s 28s
customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com created
clusterrole.rbac.authorization.k8s.io/awx-operator created
clusterrolebinding.rbac.authorization.k8s.io/awx-operator created
serviceaccount/awx-operator created
deployment.apps/awx-operator created
[null@server01 awx]$ minikube kubectl apply – -f myawx.yml
awx.awx.ansible.com/awx created
[null@server01 awx]$ watch minikube kubectl – get pods -A
[null@server01 awx]$ minikube service list
-------------|------------------------------------|--------------|---------------------------|

NAMESPACE NAME TARGET PORT URL
default awx-operator-metrics No node port
default awx-postgres No node port
default awx-service http/80 http://192.168.49.2:31377
default kubernetes No node port
kube-system ingress-nginx-controller-admission No node port
kube-system kube-dns No node port
------------- ------------------------------------ -------------- ---------------------------

[null@server01 awx]$ minikube service awx-service --url
http://192.168.49.2:31377

2

The lack of some ingress controllers not running properly is worrying:

minikube service list

---------------|------------------------------------|--------------|---------------------------|

NAMESPACE NAME TARGET PORT URL
default awx-operator-metrics No node port
default awx-postgres No node port
default awx-service http/80 http://192.168.49.2:30898
default kubernetes No node port
ingress-nginx ingress-nginx-controller http/80 http://192.168.49.2:32715

https/443 | http://192.168.49.2:31074 |
ingress-nginx | ingress-nginx-controller-admission | No node port |
kube-system | kube-dns | No node port |
---------------|------------------------------------|--------------|---------------------------|

Try using the latest minikube which is currently 1.20. 1.18 looks like it could be quite out of date as lots of images etc were updated and pulled down in 1.20
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86_64.rpm
sudo rpm -Uvh minikube-latest.x86_64.rpm

3

That’s what I originally did, I ran into the same issue. I then reread here https://github.com/ansible/awx/blob/devel/INSTALL.md#installing-awx and it states to use version 1.18.1.

My original route to install minikube:
wget https://storage.googleapis.com/minikube/releases/latest/minikube-latest.x86_64.rpm
rpm -Uvh minikube-latest.x86_64.rpm

After Reading the “Note”:
wget https://github.com/kubernetes/minikube/releases/download/v1.18.1/minikube-1.18.1-0.x86_64.rpm
rpm -Uvh minikube-1.18.1-0.x86_64.rpm

Note from Link above:
:warning: NOTE
If you’re about to install minikube or have already installed it, please be sure you’re using Minikube v1.18.1. There’s a bug right now that will not allow you to run it using Minikube v1.19.x.

4

The docs might be out of date, as minikube is now on 1.20 and they only talk about 1.19.
I’m using 1.20 with AWX 19.0 and it’s working fine and the minikube service list matches what I posted before.
The ingress controller is your problem.

I suspect everything else is running fine.
pip3 install awxkit
awx --conf.host http://192.168.49.2:31099 --conf.username admin --conf.password pcvYqZY4jd29pTkUHftkLsa4UzVBFIbRp login

awx --conf.host http://192.168.49.2:31099 --conf.username admin --conf.password pcvYqZY4jd29pTkUHftkLsa4UzVBFIbRp me
just to prove it (that’ll hit the API)

5

This might help if you’re using minikube: https://youtu.be/AYfqkTbCDAw