PostgreSQL Charm

master/standby deploy failing due to skipped reload on master

Bug #1815598 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PostgreSQL Charm
Incomplete
Critical
Stuart Bishop

Bug Description

On master branch & edge channel, master/standby deployments may fail as the master is updating its pg_hba.conf to give access to the (pending) standby, but no reload is happening so the change is not being applied. The standby then fails to clone the master.

Stuart Bishop (stub)
Changed in postgresql-charm:
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Stuart Bishop (stub)
Stuart Bishop (stub)
Changed in postgresql-charm:
status: Confirmed → Incomplete
Revision history for this message
rafi (rafise) wrote :

Having the same issue.

Revision history for this message
rafi (rafise) wrote :

NOTE** If the charm gets deployed with -n 3 seems fine but the replicas don't get any data from master the line in the master (porsgresql.conf is wal_level = logical should be hot_standby).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.