User role not existing and Postgres password not set

[JustScreaMy]

Name and Version

bitnami/postgresql 16.0.4

What architecture are you using?

amd64

What steps will reproduce the bug?

Im trying to run authentik helm chart with bitnami/postgresql as a dependency
My environment consist of

• 3 k3s nodes
• csi-driver-nfs

Are you using any custom parameters or values?

postgresql:
  image:
    debug: true
  enabled: true
  auth:
    password: testpassword
    username: authentik
    database: authentik
    postgresPassword: testpassword
  volumePermissions:
    enabled: true

What is the expected behavior?

Working PostgreSQL

What do you see instead?

I dont have my specified user created, and the password for postgres user is not set even though it is in values.yaml.

Defaulted container "postgresql" out of: postgresql, init-chmod-data (init)
postgresql 21:51:39.53 INFO  ==>
postgresql 21:51:39.53 INFO  ==> Welcome to the Bitnami postgresql container
postgresql 21:51:39.53 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 21:51:39.53 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 21:51:39.53 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
postgresql 21:51:39.54 INFO  ==>
postgresql 21:51:39.54 DEBUG ==> Configuring libnss_wrapper...
postgresql 21:51:39.54 DEBUG ==> Copying files from /opt/bitnami/postgresql/conf.default to /opt/bitnami/postgresql/conf
postgresql 21:51:39.55 INFO  ==> ** Starting PostgreSQL setup **
postgresql 21:51:39.56 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 21:51:39.56 INFO  ==> Loading custom pre-init scripts...
postgresql 21:51:39.56 INFO  ==> Initializing PostgreSQL database...
postgresql 21:51:39.57 DEBUG ==> Copying files from /bitnami/postgresql/conf to /opt/bitnami/postgresql/conf
postgresql 21:51:39.57 DEBUG ==> Ensuring expected directories/files exist...
postgresql 21:51:39.73 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 21:51:39.73 INFO  ==> Generating local authentication configuration
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /bitnami/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... %

I can see that it ends initialization here, but there is no error, no log, nothing. PVC Is created correctly.

And then it just starts again.

postgresql 21:53:38.35 INFO  ==>
postgresql 21:53:38.35 INFO  ==> Welcome to the Bitnami postgresql container
postgresql 21:53:38.35 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 21:53:38.35 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 21:53:38.35 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
postgresql 21:53:38.35 INFO  ==>
postgresql 21:53:38.36 DEBUG ==> Configuring libnss_wrapper...
postgresql 21:53:38.36 DEBUG ==> Copying files from /opt/bitnami/postgresql/conf.default to /opt/bitnami/postgresql/conf
postgresql 21:53:38.37 INFO  ==> ** Starting PostgreSQL setup **
postgresql 21:53:38.38 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 21:53:38.38 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
postgresql 21:53:38.41 INFO  ==> Loading custom pre-init scripts...
postgresql 21:53:38.41 INFO  ==> Initializing PostgreSQL database...
postgresql 21:53:38.41 DEBUG ==> Copying files from /bitnami/postgresql/conf to /opt/bitnami/postgresql/conf
postgresql 21:53:38.41 DEBUG ==> Ensuring expected directories/files exist...
postgresql 21:53:38.46 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 21:53:38.47 INFO  ==> Generating local authentication configuration
postgresql 21:53:38.47 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql 21:53:38.48 INFO  ==> Configuring replication parameters
postgresql 21:53:38.50 INFO  ==> Configuring fsync
postgresql 21:53:38.50 INFO  ==> Configuring synchronous_replication
postgresql 21:53:38.61 INFO  ==> Loading custom scripts...
postgresql 21:53:38.61 INFO  ==> Enabling remote connections
postgresql 21:53:38.62 INFO  ==> ** PostgreSQL setup finished! **

postgresql 21:53:38.63 INFO  ==> ** Starting PostgreSQL **
2025-02-05 21:53:38.713 GMT [1] LOG:  pgaudit extension initialized
2025-02-05 21:53:38.759 GMT [1] LOG:  starting PostgreSQL 15.8 on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-02-05 21:53:38.760 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-02-05 21:53:38.760 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2025-02-05 21:53:38.792 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2025-02-05 21:53:38.914 GMT [100] LOG:  database system was interrupted; last known up at 2025-02-05 21:53:25 GMT
2025-02-05 21:53:39.016 GMT [100] LOG:  database system was not properly shut down; automatic recovery in progress
2025-02-05 21:53:39.048 GMT [100] LOG:  redo starts at 0/1500660
2025-02-05 21:53:39.048 GMT [100] LOG:  invalid record length at 0/1500710: wanted 24, got 0
2025-02-05 21:53:39.048 GMT [100] LOG:  redo done at 0/1500698 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-02-05 21:53:39.080 GMT [98] LOG:  checkpoint starting: end-of-recovery immediate wait
2025-02-05 21:53:39.459 GMT [98] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.123 s, sync=0.001 s, total=0.411 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2025-02-05 21:53:39.705 GMT [1] LOG:  database system is ready to accept connections
2025-02-05 21:53:48.447 GMT [111] FATAL:  password authentication failed for user "authentik"
2025-02-05 21:53:48.447 GMT [111] DETAIL:  Role "authentik" does not exist.
        Connection matched pg_hba.conf line 1: "host     all             all             0.0.0.0/0               md5"
2025-02-05 21:53:49.455 GMT [112] FATAL:  password authentication failed for user "authentik"
2025-02-05 21:53:49.455 GMT [112] DETAIL:  Role "authentik" does not exist.
        Connection matched pg_hba.conf line 1: "host     all             all             0.0.0.0/0               md5"

And when trying to login as postgres

postgresql 2025-02-05 21:31:47.405 GMT [293[] FATAL:  password authentication failed for user "postgres"
postgresql 2025-02-05 21:31:47.405 GMT [293[] DETAIL:  User "postgres" has no password assigned.
postgresql     Connection matched pg_hba.conf line 3: "local    all             all                                     md5"

Additional information

I have tried reinstalling this chart mutiple times, everytime completely cleaning the PVCs (confirmed by checking the NFS server) and putting it into new clean namespace.

[carrodher]

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and would like to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please don't hesitate to reach out to us if you have any questions or need help.

Suppose you have any questions regarding the application, customizing its content, or utilizing technology and infrastructure. In that case, we strongly recommend that you consult the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[JustScreaMy]

Hello,
I would be happy to try to contribute solution, but I dont really know how could i provide more information to help with my case. As i said, i checked every node journalctl, looked at NFS provider logs and watched the postgresql to find any clues or errors that might help me figure out what went wrong.

I dont know if this is too much to ask, but information on how can i do more debugging would be really helpful.

creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... %

This is where logs ended, so it is giving me a clue that post-bootsrap initializaton failed, but Im not sure how can i make it more verbose on why it exited.

[JustScreaMy]

Update:
I have thought that this might be a problem because my server os choice (NixOS) and it's differences from normal Linux OSs. So i recreated the cluster from scratch on Debian 12 and the problem is still there.
So i have ruled out Operating System as an issue, going to try to change my StorageClass from NFS to something, like Longhorn to try.