statushistory uses sequence, fails in multi-env state servers
Bug #1479289 reported by
William Reade
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Horacio Durán | ||
1.24 |
Fix Released
|
Critical
|
Horacio Durán |
Bug Description
This isn't just inelegant, it's actively broken and needs to be fixed. See TestAddMissingS
tags: | added: jes status |
tags: | added: blocker |
Changed in juju-core: | |
assignee: | Ian Booth (wallyworld) → Horacio Durán (hduran-8) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | none → 1.25.0 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I proposed: reviews. vapour. ws/r/2297/ reviews. vapour. ws/r/2299/
for 1.24: http://
for master: http://
they fix the same issue in respective branches by removing the sequence and using instead mgo's own auto ids.
they also include aditional changes required for this bug to be properly fixed such as adding precision to the updated time.