nova lock/unlock api return code is not accurate
Bug #1449811 reported by
Eli Qiao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Currently, lock server api only returns 202(accepted) and 404(not found).
The api return code is not accurate.
The lock/unlock api in compute-api is a sync function, so the return code
of nova-api should be:
* 200 : successfully lock/unlock an instance
* 404 : instance not found
* 409 : locking/unlocking a locked/unlocked instance
| Changed in nova: | |
| assignee: | nobody → Eli Qiao (taget-9) |
| Changed in nova: | |
| status: | New → Confirmed |
| tags: | added: api |
| Changed in nova: | |
| importance: | Undecided → Wishlist |
| assignee: | Eli Qiao (taget-9) → nobody |
Revision history for this message
| Robert Ellis (bob-ellis42) wrote | #1 |
| Changed in nova: | |
| assignee: | nobody → Robert Ellis (bob-ellis42) |
| Changed in nova: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on nova (master) | #2 |
Revision history for this message
| Robert Ellis (bob-ellis42) wrote | #3 |
| Changed in nova: | |
| assignee: | Robert Ellis (bob-ellis42) → nobody |
| status: | In Progress → Confirmed |
| Changed in nova: | |
| assignee: | nobody → stgleb (gstepanov) |
| status: | Confirmed → In Progress |
Revision history for this message
| Sean Dague (sdague) wrote | #4 |
| Changed in nova: | |
| status: | In Progress → Confirmed |
| assignee: | stgleb (gstepanov) → nobody |
To post a comment you must log in.
Claiming bug. Plan on submitting fix within 2 weeks.