telegraf is confused about its pgsql relations
Bug #1814546 reported by
Junien F
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pgsql Interface for charms.reactive |
Triaged
|
High
|
Unassigned | ||
Bug Description
Hi,
juju 2.5 - I have a model with 2 primary applications deployed, apache2 and postgresql. telegraf is related to both applications.
On the telegraf unit living on the apache2 unit, the pgsql interface sets the flag "postgresql.
< stub> axino: I think cleaner than that and I need to update interface:pgsql
This bug is here to track this work :)
Thanks !
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in interface-pgsql: | |
| status: | New → Triaged |
| importance: | Undecided → High |
To post a comment you must log in.
Investigate if it is possible to stop interface:pgsql setting the relation flags when the unit is a subordinate not co-hosted with a PostgreSQL principal.
Consider if this is better handled in charms.reactive.