statushistory uses sequence, fails in multi-env state servers

Bug #1479289 reported by William Reade
8
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 TestAddMissingServiceStatuses in state; it'll be in RB2255 if it hasn't landed yet.

Curtis Hovey (sinzui)
tags: added: jes status
tags: added: blocker
Ian Booth (wallyworld)
Changed in juju-core:
assignee: Ian Booth (wallyworld) → Horacio Durán (hduran-8)
Changed in juju-core:
status: Triaged → In Progress
Revision history for this message
Horacio Durán (hduran-8) wrote :

I proposed:
for 1.24: http://reviews.vapour.ws/r/2297/
for master: http://reviews.vapour.ws/r/2299/
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.

Changed in juju-core:
milestone: none → 1.25.0
Changed in juju-core:
status: In Progress → Fix Committed
Martin Packman (gz)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.