find-endpoints errors when application is removed
Bug #1702901 reported by
Richard Harding
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
Using the CMR feature flag:
I've deployed mysql into one model, created an offer, and used it in two other models.
When I remove the application (I broke it and hit an error state) I could remove the application just find but then find-endpoints errors. I have other offers available and so having one removed causes total failure of output in the command.
On top of that the status of my applications that were using the offered endpoint have no status change and appear as if they're working. The SaaS line in juju status should at least show the issue to the consumer and it seems that there should be some sort of relation breaking events triggered on the related applications so that the charms can process the loss of the relation endpoint.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
Revision history for this message
| Ian Booth (wallyworld) wrote | #2 |
| Changed in juju: | |
| milestone: | none → 2.3-alpha1 |
| importance: | Undecided → High |
| status: | New → In Progress |
| assignee: | nobody → Ian Booth (wallyworld) |
Revision history for this message
| Ian Booth (wallyworld) wrote | #3 |
Revision history for this message
| Ian Booth (wallyworld) wrote | #4 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
RE: surfacing the status of offered applications and propagating to related apps etc - this bit is not done yet but will be soon hopefully