Comment 6 for bug 2034014

So, rethinking about this bug I think there is one main suboptimal design:
1) maas retries the requests internally up to 90 seconds -> this is making the original request **synchronous** for the client, which is wrong.
2) the client is not retrying the request.

Right now MAAS includes a `Retry-After` header only if it would return 503 (and our gomaasclient is looking for it to retry the requests).

My proposal would be that MAAS should include a `Retry-After` header also for 409 responses and the gomaasclient should handle it and retry the requests properly.