Unhelpful error message when trying to force detach and content-type header is missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Matt Riedemann | ||
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
I was trying to force detach a volume using curl like so:
curl -d '{"os-force_
And I'd get this error message back:
{"badRequest": {"message": "There is no such action: None", "code": 400}}
When I dug into the cinder-api logs, I saw this:
Feb 16 16:08:49 queens <email address hidden>[1549]: DEBUG cinder.
Changing the 'accept' header to 'content-type' fixed it:
curl -d '{"os-force_
I get a policy error since I'm not an admin (default policy rule on this API is admin-only), but it went through properly:
{"forbidden": {"message": "Policy doesn't allow volume_
The bug is that the missing content-type results in a very unhelpful error message.
Changed in cinder: | |
importance: | Undecided → Low |
Changed in nova: | |
status: | In Progress → Confirmed |
assignee: | Matt Riedemann (mriedem) → nobody |
Fix proposed to branch: master /review. openstack. org/545378
Review: https:/