[postgresql] bug: password authentication failed for user "postgres" #2061
Description
Which chart:
postgresql v8.6.4
Description
Admin user (postgres) password fails with or without default settings.
Steps to reproduce the issue:
- Setup a values.yaml file like below:
replication:
enabled: false
slaveReplicas: 2
synchronousCommit: "on"
numSynchronousReplicas: 1
applicationName: artifactory
# existingSecret: postgresql-admin-user-creds
postgresqlDatabase: artifactory
persistence:
size: 100Gi
metrics:
enabled: true- Install it using helm
helm install artifactory -f postgresql-values.yaml bitnami/postgresql
Describe the results you received:
Error text:
artifactory-postgresql postgresql 16:16:57.76 INFO ==> ** Starting PostgreSQL setup **
artifactory-postgresql postgresql 16:16:57.81 INFO ==> Validating settings in POSTGRESQL_* env vars..
artifactory-postgresql postgresql 16:16:57.82 INFO ==> Loading custom pre-init scripts...
artifactory-postgresql postgresql 16:16:57.82 INFO ==> Initializing PostgreSQL database...
artifactory-postgresql postgresql 16:16:57.84 INFO ==> postgresql.conf file not detected. Generating it...
artifactory-postgresql postgresql 16:16:57.85 INFO ==> pg_hba.conf file not detected. Generating it...
artifactory-postgresql postgresql 16:16:57.85 INFO ==> Generating local authentication configuration
artifactory-postgresql postgresql 16:16:57.86 INFO ==> Deploying PostgreSQL with persisted data...
artifactory-postgresql postgresql 16:16:57.86 INFO ==> Configuring replication parameters
artifactory-postgresql postgresql 16:16:57.89 INFO ==> Configuring fsync
artifactory-postgresql postgresql 16:16:57.89 INFO ==> Loading custom scripts...
artifactory-postgresql postgresql 16:16:57.90 INFO ==> Enabling remote connections
artifactory-postgresql postgresql 16:16:57.91 INFO ==> Stopping PostgreSQL...
artifactory-postgresql postgresql 16:16:57.91 INFO ==> ** PostgreSQL setup finished! **
artifactory-postgresql postgresql 16:16:57.97 INFO ==> ** Starting PostgreSQL **
artifactory-postgresql 2020-03-16 16:16:57.991 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
artifactory-postgresql 2020-03-16 16:16:57.992 GMT [1] LOG: listening on IPv6 address "::", port 5432
artifactory-postgresql 2020-03-16 16:16:57.997 GMT [1] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
artifactory-postgresql 2020-03-16 16:16:58.011 GMT [165] LOG: database system was shut down at 2020-03-16 16:16:26 GMT
artifactory-postgresql 2020-03-16 16:16:58.019 GMT [1] LOG: database system is ready to accept connections
artifactory-postgresql 2020-03-16 16:16:58.922 GMT [172] FATAL: password authentication failed for user "postgres"
artifactory-postgresql 2020-03-16 16:16:58.922 GMT [172] DETAIL: Password does not match for user "postgres".
artifactory-postgresql Connection matched pg_hba.conf line 1: "host all all 0.0.0.0/0 md5"
artifactory-postgresql 2020-03-16 16:17:00.924 GMT [173] FATAL: password authentication failed for user "postgres"
artifactory-postgresql 2020-03-16 16:17:00.924 GMT [173] DETAIL: Password does not match for user "postgres".
artifactory-postgresql Connection matched pg_hba.conf line 1: "host all all 0.0.0.0/0 md5"
metrics time="2020-03-16T16:16:57Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
metrics time="2020-03-16T16:16:58Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
metrics time="2020-03-16T16:17:00Z" level=info msg="Established new database connection to \"127.0.0.1:5432\"." source="postgres_exporter.go:878"
metrics time="2020-03-16T16:17:03Z" level=error msg="Error opening connection to database (postgresql://postgres:[email protected]:5432/artifactory?sslmode=disable): pq: password authentication failed
metrics time="2020-03-16T16:17:03Z" level=info msg="Starting Server: :9187" source="postgres_exporter.go:1672"
Describe the results you expected:
I expected it to work.
Additional information you deem important (e.g. issue happens only occasionally):
Note that this happens the same way if you un-comment the existingSecret line.
Version of Helm and Kubernetes:
- Output of
helm version:
version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}- Output of
kubectl version:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:30:10Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.9", GitCommit:"500f5aba80d71253cc01ac6a8622b8377f4a7ef9", GitTreeState:"clean", BuildDate:"2019-11-13T11:13:04Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}