state: initially assigned units don't get storage attachments
Bug #1517344 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Critical
|
Nate Finch | ||
Bug Description
See lp:1516144
The new unit assigner code has changed some of the behaviour around assigning units to machines, turning previously non-atomic operations into atomic ones. This has uncovered a latent bug: when a unit is assigned to a new machine, that machine will not get storage attachments.
| Changed in juju-core: | |
| milestone: | 1.26-alpha2 → 1.26-beta1 |
| tags: | added: bug-squad |
| tags: | added: regression |
| Changed in juju-core: | |
| importance: | High → Critical |
| Changed in juju-core: | |
| milestone: | 1.26-beta1 → 1.26-alpha2 |
| Changed in juju-core: | |
| assignee: | nobody → Nate Finch (natefinch) |
Revision history for this message
| Nate Finch (natefinch) wrote | #1 |
Revision history for this message
| Cheryl Jennings (cherylj) wrote | #2 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| tags: | added: 2.0-count |
To post a comment you must log in.
I have a fix for this... we were trying to read the database to find the storage constraints during service deployment, so obviously the constraints hadn't been written yet.
I have to write a test for this, but it's late, so I'll do that in the morning.