Postgresql service is not being restarted after charms edits pg_hba.conf from adding a juju relation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PostgreSQL Charm |
New
|
Undecided
|
Unassigned |
Bug Description
When adding a juju relation to postgresql charm new information is being added to pg_hba.conf
Example:
./12/main/
./12/main/
./12/main/
./12/main/
./12/main/
./12/main/
Note: This is a juju cross model relation.
However, postgresql service is not being restarted after this file is edited. Thus, not allowing related charms to properly connect to the database because of whitelist not being reloaded.
Output of trying to manually connect to postgresql service using psql cli from one of the related charms:
psql -h 3.93.194.50 -U juju_remote-
psql: error: connection to server at "3.93.194.50", port 5432 failed: FATAL: pg_hba.conf rejects connection for host "54.157.207.104", user "juju_remote-
connection to server at "3.93.194.50", port 5432 failed: FATAL: pg_hba.conf rejects connection for host "54.157.207.104", user "juju_remote-
A similar behaviour happens after changing postgresql charm configs
Ex. juju config postgresql extra_pg_auth="host all all 0.0.0.0/0 md5"
Information will get rendered inside pg_hba.conf but service would not have been restarted after it.