Pre-fetching oauth consumer from SSO results in a 500
Bug #873228 reported by
Michael Nelson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Invalid
|
High
|
Unassigned | ||
Ratings and Reviews server |
Invalid
|
Low
|
Unassigned | ||
Software Center Agent |
Invalid
|
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_
BadStatusLine: https:/
SSO 500's itself: https:/
No content-type in response: https:/
tags: | added: oops |
Changed in canonical-identity-provider: | |
importance: | Undecided → High |
Changed in canonical-identity-provider: | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
Changed in software-center-agent: | |
status: | New → Confirmed |
importance: | Undecided → Low |
To post a comment you must log in.
As for the 500 responses in SSO itself, this is the traceback from one of them: https:/ /pastebin. canonical. com/54332/