*-relation-broken has no way to identify which remote service is being broken
Bug #791042 reported by
Clint Byrum
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Medium
|
Unassigned |
Bug Description
While working on the mysql formula, I needed a way to record the fact that a relation had been broken, so that when it was re-added, the code path would be slightly different since the database already existed.
Unfortunately, the environment doesn't seem to contain an indicator as to which relationship is broken. ENSEMBLE_RELATION only tells me which of my relations are being broken, but not what remote service has been unrelated.
The workaround is to run 'relation-list' which seems to somehow know which relationship is being broken and only return the members of it. Whatever it uses to know that, should be exposed to the hook in the environment.
Changed in ensemble: | |
importance: | Undecided → Medium |
milestone: | none → dublin |
Changed in ensemble: | |
status: | New → Confirmed |
Changed in ensemble: | |
milestone: | dublin → none |
Changed in juju: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
This will also be solved by implementing the feature described in #791370. Marking as a duplicate, and copy & pasting the use case.