OperationalError (the exception raised when a serialization error occurs) leads to a 500 response instead of a 503 response

Bug #1412690 reported by Raphaël Badin on 2015-01-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The type of exception raised when (despite the retries) a serialization error happens is OperationalError; it generates a 500 (Internal Server Error) instead of a 503 (Service Unavailable) with a Retry-After header.

Returning a 503 + Retry-After header will allow clients to retry the request (the Juju client does that already for instance) and possibly cope with this transient exception.

Changed in maas:
milestone: none → 1.8.0
Changed in maas:
milestone: 1.8.0 → 1.9.0
no longer affects: maas/1.8
Andres Rodriguez (andreserl) wrote :

We no longer believe this is an issue with the latest versions of MAAS.

Changed in maas:
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