OOPS when handling a bad api request

Bug #1271482 reported by Michael Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Confirmed
Medium
Unassigned

Bug Description

Steps to reproduce:
 * GET https://sc.staging.ubuntu.com/api/2.0/click-user-can-download/ (ie. no query data)
Expected result:
 * BadRequest returned
Actual result:
 * Oops [1]

The issue is that the system piston is being used, which uses django internals (HttpResponse._get_content) which are no longer there with Django 1.5. It has been fixed in the sourcecode version of piston that we have deployed, but the system version is imported before we have setup our import paths in the deploy config (you can reproduce the issue in dev [2]).

[1] https://oops.canonical.com/?oopsid=OOPS-fdb3ec6932eb41de81119ddf81ca7b64 , traceback for posterity: https://pastebin.canonical.com/103381/
[2] https://pastebin.canonical.com/103460/

description: updated
Revision history for this message
Tong-Wook Shinn (tshinn) wrote :

This no longer occurs. We can probably close this.

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.