Pre-fetching oauth consumer from SSO results in a 500

Bug #873228 reported by Michael Nelson on 2011-10-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical SSO provider
High
Unassigned
Ratings and Reviews server
Low
Unassigned
Software Center Agent
Low
Unassigned

Bug Description

We had an abnormal number of oops reports for 2011-10-122, 10 in total, but 8 of which are all related to errors while contacting SSO via a lazr.restfulclient. AFAICT, looking at the calendar, there was no SSO deploy yesterday (and I doubt there would have been production changes due to the release). Here are the three types of errors (all during prefetch_oauth_consumer):

BadStatusLine: https://pastebin.canonical.com/54290/
SSO 500's itself: https://pastebin.canonical.com/54291/
No content-type in response: https://pastebin.canonical.com/54293/

tags: added: oops
Anthony Lenton (elachuni) wrote :

As for the 500 responses in SSO itself, this is the traceback from one of them: https://pastebin.canonical.com/54332/

Changed in canonical-identity-provider:
importance: Undecided → High
Changed in canonical-identity-provider:
status: New → Confirmed
status: Confirmed → Triaged
Dave Morley (davmor2) on 2012-11-16
Changed in software-center-agent:
status: New → Confirmed
importance: Undecided → Low
Daniel Manrique (roadmr) wrote :

Old enough that the involved components have probably changed enough that this is invalid at this point. Feel free to reopen if it happens again.

Changed in rnr-server:
status: Confirmed → Invalid
Changed in software-center-agent:
status: Confirmed → Invalid
Changed in canonical-identity-provider:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers