-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Redis Dump Permissions Error Cause AWX Exceptions #9401
Comments
Having the same issue on 17.0.1. Upddate: The issue came back after a restart at some point |
I was able to do this, but I also tried adding To me it looks like Redis is executing the RDB snapshots by default whereas before it did not. |
Hi folks. Are you by chance using this option? Or maybe your Kubernetes clusters are forcing running containers as a non-root user? I noticed that the entrypoint for redis uses gosu to switch users inside of the container. This might be part of the problem. |
Same error for us after a restart. |
The entrypoint for redis is the same between 6.0 and 6.2 but nothing stands out in the change log to me of what changed to cause it unless its tied to one of the security updates. I'm no Redis expert though. I was able to replicate the issue using the same redis.conf in a bare redis container by setting the run-as user to anything other than "999" on all three versions that I tested. 6.0.10, 6.0.11, and 6.2.0. |
@Tioborto I modified the setting and ran it on a new install but by only changing |
Hello @danukefl,
|
For me @danukefl 's solution works so far, adding |
I am also having success with @danukefl's solution. |
👋 Hey everyone, this should be resolved in the latest version of AWX (17.1.0). |
ISSUE TYPE
SUMMARY
On a fresh install of AWX 17.0.1, Redis returns an exception preventing most functionality, including job execution after an uptime of a few minutes.
ENVIRONMENT
STEPS TO REPRODUCE
Ansible-playbook install to Kubernetes cluster only modifying the cluster information, ingress, and credential values as required. Postgres was setup through the playbook using Helm.
One sign in, credentials were changed, Gitlab credential added, Gitlab Project added, all project sync jobs fail with no Output display and status of "Failed". Relaunching the job provides and error with
POST /api/v2/projects/6/update/ 500
Restart the AWX deployment and jobs are successful for a few minutes until Redis errors occur after approximately 5 minutes when background saving starts.
EXPECTED RESULTS
Project sync job to execute successfully
ACTUAL RESULTS
All jobs fail, some settings cannot be configured, various errors throughout all of AWX
ADDITIONAL INFORMATION
Based on search results for the error relating to Redis, in redis-cli the command
config set stop-writes-on-bgsave-error no
should be executed since there isn't the need for data persistence for AWX.awx-redis
awx-task
awx-web
The text was updated successfully, but these errors were encountered: