[traceback] BugzillaRestHTTPUnexpectedError
Categories
(Socorro :: Antenna, defect, P3)
Tracking
(Not tracked)
People
(Reporter: relud, Assigned: relud)
Details
Attachments
(1 file)
https://mozilla.sentry.io/issues/6090433828
message: status code: 200, payload: b'{"error":true,"documentation":"https://bmo.readthedocs.io/en/latest/api/","code":100500,"message":nu'
traceback:
BugzillaRestHTTPUnexpectedError: status code: 200, payload: b'{"error":true,"documentation":"https://bmo.readthedocs.io/en/latest/api/","code":100500,"message":nu'
File "django/core/handlers/exception.py", line 55, in inner
response = get_response(request)
File "django/core/handlers/base.py", line 197, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "crashstats/crashstats/utils.py", line 216, in wrapper
response = f(request, *args, **kw)
File "crashstats/crashstats/views.py", line 351, in buginfo
return bzapi.get(bug_ids)
File "crashstats/crashstats/models.py", line 1046, in get
raise BugzillaRestHTTPUnexpectedError(
this previously caused a KeyError because the payload json object didn't contain "bugs"
like we expect. We should probably modify the message here to use "message" from the payload when "error" is true.
Assignee | ||
Updated•3 months ago
|
Comment 1•3 months ago
|
||
I think I truncated the response payload at 100 characters--we should increase that to like 200. 100 wasn't enough to get context.
Assignee | ||
Comment 2•2 months ago
|
||
Assignee | ||
Comment 3•2 months ago
|
||
Assignee | ||
Comment 4•2 months ago
|
||
PR deployed in v2024.12.10
Assignee | ||
Comment 5•2 months ago
|
||
A second event has come in with the message: b'{"message":null,"code":100500,"documentation":"https://bmo.readthedocs.io/en/latest/api/","error":tr'
That looks like the full message may be {"error":true,"documentation":"https://bmo.readthedocs.io/en/latest/api/","code":100500,"message":null}
, but we'll find out more when the next message comes in now that we've increased to 200 characters.
Looking at the linked docs, there's no mention of error 100500. Error 100 is "invalid bug alias", and I don't expect this has anything to do with that because this error appears to be transient. I think this is supposed to be an HTTP 500, but bugzilla isn't handling it correctly.
For now I'm going to wait until the next error comes in.
Assignee | ||
Comment 6•28 days ago
•
|
||
we finally got a new event that confirms the full message is {"error":true,"documentation":"https://bmo.readthedocs.io/en/latest/api/","code":100500,"message":null}
. I will file a PR to retry this error, and otherwise treat it as a 500.
Description
•