You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Got password authentication failed and upgrade never be completed.
TASK [Stream backup from pg_dump to the new postgresql container] ********************************
fatal: [localhost]: FAILED! => {"changed": true, "failed_when_result": true, "rc": 1, "return_code": 1, "stderr": "pg_dump: error: connection to database \"awx\" failed: connection to server at \"awx-postgres.awx.svc\" (10.42.0.23), port 5432 failed: FATAL: password authentication failed for user \"awx\"\npg_restore: error: input file is too short (read 0, expected 5)\n", "stderr_lines": ["pg_dump: error: connection to database \"awx\" failed: connection to server at \"awx-postgres.awx.svc\" (10.42.0.23), port 5432 failed: FATAL: password authentication failed for user \"awx\"", "pg_restore: error: input file is too short (read 0, expected 5)"], "stdout": "", "stdout_lines": []}
Additional information
No response
Operator Logs
No response
The text was updated successfully, but these errors were encountered:
Please confirm the following
Bug Summary
Upgrade AWX Operator from 0.25.0 to later version failed due to special characters in the password for PostgreSQL.
In the current implementation, PGPASSWORD has been passed without quotes during upgrading PostgreSQL 12 to 13.
If
awx_postgres_pass
contains any special characters such as$
,#
, etc. that has special meaning for shell, the command will be broken.AWX Operator version
1.1.3
AWX version
21.10.2
Kubernetes platform
kubernetes
Kubernetes/Platform version
k3s version v1.25.4+k3s1
Modifications
no
Steps to reproduce
Deploy old AWX
Upgrade AWX
Expected results
New AWX Operator upgrades AWX with success.
Actual results
Got
password authentication failed
and upgrade never be completed.Additional information
No response
Operator Logs
No response
The text was updated successfully, but these errors were encountered: