cross model incorrect offer-uuid
Bug #2012583 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Critical
|
Ian Booth | ||
Bug Description
On the offering side of a cross model relation, we create a remove application proxy for the consuming app. This has a single offer-uuid attribute.
But, the consuming app can be related to more than one offer, and the attribute becomes meaningless - first one wins.
It is used to serve the app icon (not needed any more) and also ref count when removing an offer.
We need to remove the incorrect attribute and adjust how offer removal is done.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| importance: | High → Critical |
| Changed in juju: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| Changed in juju: | |
| status: | Triaged → In Progress |
Revision history for this message
| Ian Booth (wallyworld) wrote | #2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm marking this as critical for 2.9.43
If you have a model with 2 offers off the one application, model migration fails with a txn assertion error. I have not tracked it down, but I think this issue is related.