Comment 2 for bug 1749797

Ah, gotcha. That makes sense, thanks Chris.

I do think we should make placement's error message better for the client. Currently it is: {"message": "The server is currently unavailable. Please try again at a later time.<br /><br />\n\n\n", "code": "503 Service Unavailable", "title": "Service Unavailable"}. See also the compute logs from the same run: http://logs.openstack.org/50/544750/8/check/ironic-grenade-dsvm-multinode-multitenant/5713fb8/logs/screen-n-cpu.txt.gz#_Feb_15_17_58_22_470073

I'm thinking we can catch webob.exc.HTTPServiceUnavailable from placement's wrapper around the auth_token middleware, and transform the message there. Does that work for you?