changing backup_dir config did not result in backups going to the new value

Bug #1864549 reported by Sheila Miguez on 2020-02-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PostgreSQL Charm
Critical
Unassigned

Bug Description

I deployed a postgresql charm to an environment without altering the default backup_dir setting (/var/lib/postgresql/backups).

After I realized that storage didn't include the default backup_dir, I changed the config to point to a new location, /srv/pgdata/backups.

The new location does not exist, and backups are still going to the original directory.

Stuart Bishop (stub) wrote :

The scripts get updated on upgrade-charm, but not the config-changed hook. The postgresql.cluster.support-scripts flag needs to be cleared on configuration change.

Changed in postgresql-charm:
status: New → Triaged
importance: Undecided → Critical
Stuart Bishop (stub) on 2020-02-25
Changed in postgresql-charm:
status: Triaged → Fix Committed
Stuart Bishop (stub) on 2020-02-26
Changed in postgresql-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers