master/standby deploy failing due to skipped reload on master
Bug #1815598 reported by
Stuart Bishop
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.
| Changed in postgresql-charm: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → Stuart Bishop (stub) |
| Changed in postgresql-charm: | |
| status: | Confirmed → Incomplete |
Revision history for this message
| rafi (rafise) wrote | #1 |
Revision history for this message
| rafi (rafise) wrote | #2 |
To post a comment you must log in.
Having the same issue.