-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWX 13 broken due upstream issues #18
Comments
memcached was removed from awx in 12, I'd guess we need to change this role to reflect the upstream changes in kubernetes role; CCing @cfelder ansible/awx#7240 |
https://github.com/ikke-t/awx_pod/blob/master/templates/settings.py.j2 and https://github.com/ansible/awx/blob/devel/installer/roles/kubernetes/templates/deployment.yml.j2 don't have my test setup ready at the moment so I won't get around to that soon :D |
I suppose the order of getting this back to work would be to submit PRs to awx about those two starter script execute bits. Then waiting to get the upstream containers being rebuilt to work with PR changes. Once having those in place, there is place to make and test the above changes to drop memcached and update settings. Creating the PR is small job, I wonder if @cfelder already has the changes in his repo? I have a bit quieter time at work than usual, I could also do some of this one day. |
I am already on it (removing memcache). I'll also post an example playbook here to run with a derived container image which has already fixed executable bits. If I'll find the correct spot in the awx repo I can make a PR as well for fixing those Dockerfiles. |
memcached has been removed upstream in awx 12 Related: ikke-t#18
The following example uses a derived container with fixed acls and removed preloading data into awx as well.
Dockerfile
needs: #19 |
If I recall right awx assumes it runs priviledged, so you won't need to change the runscripts but add priviledged to the web container. With 11 it seems this was optional for the web container, now that they are not seperated anymore it seems mandatory. |
and for the no preload, I am guessing you could just configmap a launch_awx_task.sh into the image, then you don't need to rebuild it. But that would make a fine upstream change, create a env variable that you can set to skip it :) |
please review if these changes fix the issues, I could just press the PR button: ansible/awx@6c107db |
|
@cfelder https://github.com/ikke-t/awx_pod/blob/master/templates/awx.yml.j2#L216-L217 that also for the web container, that should help :) |
I am still getting
although I added securityContext... Looks like privileged: True is not honored in kube play when using
the shell script is executed correctly. Nevertheless shouldn't running unprivileged containers be preferred? |
It should be honoured, otherwise the tasks container should have never been working :) but upstream also changed the security context to unpriviledged for all containers: so maybe there is something else in the deployment that has changed (or the deployment really was never working for upstream 13) |
Hello guys, |
Not sure if this is progress, or chasing a red herring, but,
Running the podman play command from the systemd service, I get the awx to start, but the logs: Traceback (most recent call last): |
See #19 which removes memcache |
Thanks I applied those changes, as well as the securityContext I mentioned earlier, and now I have a working podman awx 13.0.0 thanks. |
Why does the web container need to be privileged? Sounds like there are some permission fixes to be done, normally any web server should not need any special privileges. |
Or was that just to go around the fact that launchers were missing execute bits for the groups and others? That fix is btw now merged in to awx. |
Yes, since only root could execute: bash-4.4# ls -l /usr/bin/launch_awx.sh Good to know that it has been fixed. |
Permission issues:
So let's label awx_pod with 13.0 once those are fixed. This module is broken due those ATM at master branch. If you want to use a working module, select earlier version.
The text was updated successfully, but these errors were encountered: