state: ensure that Models are always paired with the correct State
Bug #1570269 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
| 2.2 |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
We sometimes leak state.Model objects with a state.State inside that was not opened for the same model. This can lead to surprising behaviour if you call methods on the Model. I've guarded most if not all of the methods against accidents now, but it's easy to get wrong.
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| milestone: | none → 2.1.0 |
| Changed in juju: | |
| milestone: | 2.1-rc2 → none |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| importance: | Medium → Low |
| Changed in juju: | |
| importance: | Low → High |
| milestone: | none → 2.2.2 |
| milestone: | 2.2.2 → none |
| Changed in juju: | |
| milestone: | none → 2.3-alpha1 |
| Changed in juju: | |
| status: | Triaged → Fix Committed |
| assignee: | nobody → Andrew Wilkins (axwalk) |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #2 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
As this is a tech-debt item, I am lowering its Importance.