keystone should return 503 service unavailable when service can't get a token via admin user/pass
Bug #942984 reported by
Joseph Heck
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Critical
|
Jesse Andrews |
Bug Description
the service should send 503 "service unavailable" when the service can't get a token via admin user/pass to validate with --- and LOG why it is failing!
from : http://
the service should send 503 "service unavailable" when the service can't get a token via admin user/pass to validate with --- and LOG why it is failing!
(related to bug #942983)
(depends on bug #942979)
Changed in keystone: | |
milestone: | essex-rc1 → essex-4 |
Changed in keystone: | |
assignee: | nobody → anotherjesse (anotherjesse) |
Changed in keystone: | |
milestone: | essex-4 → essex-rc1 |
Changed in keystone: | |
status: | Confirmed → In Progress |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
503 is not the right return Code. 503 is a in internal server error for a valid request. 403 would be appropriate, and in keeping with the design decisions made elsewhere in Keystone.