API 2 does not ensure the latest revision is selected

Bug #1219064 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charmworld
Fix Released
Critical
Aaron Bentley

Bug Description

The "charm" API endpoint should select the latest revision, but it does not. For example, http://staging.jujucharms.com/api/2/charm/precise/rails should select revision 1 or later, but instead selects revision 0. (This is presumably because mongodb falls back to insertion order.)

As of r371, API3 is not affected, but manage.jujucharms.com currently is running an older revno.

Related branches

Aaron Bentley (abentley)
description: updated
Aaron Bentley (abentley)
Changed in charmworld:
assignee: nobody → Aaron Bentley (abentley)
status: Triaged → In Progress
Aaron Bentley (abentley)
Changed in charmworld:
status: In Progress → 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.