attachment update API returns 500 when it should return 400
Bug #1907295 reported by
Eric Harney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
In Progress
|
Medium
|
Eric Harney |
Bug Description
This code:
causes this code:
"Prevent double-attachment race in attachment_reserve"
https:/
https:/
to return an HTTP 500 for the "duplicate connectors detected on volume" case. This should return an HTTP 400 instead.
Changed in cinder: | |
assignee: | nobody → Eric Harney (eharney) |
tags: | added: attachment exception status-code volume |
Changed in cinder: | |
status: | New → Triaged |
importance: | Undecided → Low |
importance: | Low → Medium |
To post a comment you must log in.
Looking closer at this, I'm not sure why, since the attachments API code should be catching InvalidVolume. Maybe reraising InvalidVolume doesn't result in the right error code being returned via the API?