-
Notifications
You must be signed in to change notification settings - Fork 629
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 database migration job fail when using custom CA certificate #1782
Comments
@akkaba23 you are configuring the ca cert used by postgres via |
@akkaba23 could you please these the changes in this PR out? |
hi @rooftopcellist, Thank you for the reply. Yes, I am configuring the ca cert used by postgres via the |
The same issue also happens for the Here is my update for task.yaml.j2:
code:
|
@YassineFadhlaoui @akkaba23 |
Thanks @JoelKle for taking the time and creating a PR |
Hello @rooftopcellist and @TheRealHaoLiu, Just a gentle reminder about this issue that is a blocker in order to upgrade to a newer version. Is there anything we can do to help you? |
Please confirm the following
Bug Summary
During the upgrade to awx 24.0.0, a new pod is created for migration. This pod doesnt contain the custom ca certificate and fails when using external postgres with verify enabled.
AWX Operator version
2.13.1
AWX version
24.0.0
Kubernetes platform
kubernetes
Kubernetes/Platform version
1.27.11
Modifications
no
Steps to reproduce
Update from awx 23.8.1 to 24.0.0
Add custom ca certs with external postgres.
Expected results
migration pod run with custom ca certs added and migration finishes in task pods.
Actual results
no custom ca certs added and pod failing with django.db.utils.OperationalError: connection failed: certificate verify failed
Additional information
File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/psycopg/connection.py", line 728, in connect
raise ex.with_traceback(None)
django.db.utils.OperationalError: connection failed: certificate verify failed
Operator Logs
No response
The text was updated successfully, but these errors were encountered: