Database configuration is not updated after changing relation
Bug #2057907 reported by
Nikita Koltsov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Charm |
Confirmed
|
High
|
Mitch Burton | ||
Bug Description
Charm revision: 107
I tried to install pgbouncer in between landscape and postgessql charm. To avoid hitting max connection limits on the big system: https:/
The steps to reproduce:
1. Add pgbouncer to the deployment
2. Relate pgbouncer to postgress
3. remove relation in between postgessql and landscape
4. Relate pgbouncer to landscape
The result is database information is not udpated in the landscape configuration
I suggest that just removing relation should be enough to see that hooks are not triggering properly
| Changed in landscape-charm: | |
| importance: | Undecided → High |
| assignee: | nobody → Mitch Burton (mitchburton) |
Revision history for this message
| Mitch Burton (mitchburton) wrote | #1 |
| Changed in landscape-charm: | |
| status: | New → Confirmed |
To post a comment you must log in.
In testing, when adding the relation between pgbouncer and landscape-server:
unit-pgbouncer-3: 11:26:06 WARNING unit.pgbouncer/
Could be related that pgbouncer does not support multiple databases: https:/
This seems like a blocker to using pgbouncer - we'd need 6 different ones, one for each database that landscape-server connects to.