-
Notifications
You must be signed in to change notification settings - Fork 637
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
Add postgres init container to resolve permissions for some k3s deployments: init container commands fail with permission denied #1999
Comments
It should work, might be related to the indentation on the Also try it without:
And see if that makes any different for the init container |
Hi @kcjones91 , It works. You have a wrong indentation in your file for The instruction in #1805 solve the issue for me and I have the same version of AWX. Best Regards, |
This was my mistake. I did fix this issue before asking the question and removed that value:
|
Sorry this was my typo. I fixed this before testing. It initially would not apply my configuration due to indention. But I did have that same error. |
The issue was Selinux:
I am using vanilla k8s on Fedora. I tried to update above, but this solved the issue. |
Please confirm the following
Bug Summary
I am running into this on my end. Probably an easy fix?
AWX Operator version
2.19.1
AWX version
24
Kubernetes platform
kubernetes
Kubernetes/Platform version
K8s
Modifications
no
Running on Fedora 41
Steps to reproduce
Fresh install of AWX following the helm chart deployment guide. I followed this issue: #1805, tracking the issue for the fresh deployment. I attempted deploy AWX with my current configuration:
When I apply the configuration I recieve the following error:
Expected results
AWX deployed with a working persistent database.
Actual results
Additional information
No response
Operator Logs
No response
Tasks
Tasks
The text was updated successfully, but these errors were encountered: