Closed Bug 1901998 Opened 1 year ago Closed 1 year ago

[traceback] RetryError: bugzilla 502 for /rest/bug

Categories

(Socorro :: Webapp, defect, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

Details

Attachments

(1 file)

Sentry: https://mozilla.sentry.io/issues/5415508722/events/2ce184818d78461a90ade1fef1f35b51/

Release: :cf09fe93 (stage environment, but we see this in prod, too)

Traceback:

RetryError: HTTPSConnectionPool(host='bugzilla.mozilla.org', port=443): Max retries exceeded with url: /rest/bug?id=1856672&include_fields=summary,status,id,resolution (Caused by ResponseError('too many 502 error responses'))
  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 335, in buginfo
    result = bzapi.get(bug_ids)
  File "crashstats/crashstats/models.py", line 1044, in get
    response = session.get(url, headers=headers)
  File "requests/sessions.py", line 602, in get
    return self.request("GET", url, **kwargs)
  File "requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "socorro/lib/librequests.py", line 33, in send
    return super().send(*args, **kwargs)
  File "requests/adapters.py", line 691, in send
    raise RetryError(e, request=request)

Bugzilla returns a 502 for some period of time which exceeds our retry logic in the /buginfo/bug view. This happens semi-regularly. We should probably adjust how retrying works and make it more resilient to reduce the errors.

This went to prod in: https://github.com/mozilla-services/socorro/releases/tag/v2024.11.01

It's hard to verify this, so I'm going to close it out and we can reopen if it happens again.

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: