Random Bad Request Responses from Cinder API calls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Wishlist
|
Unassigned |
Bug Description
Randomly receive 400 responses from Cinder API when trying to do things like delete volumes.
jgriffith@trusty ~ $ cinder delete 44f832a6-
Delete for volume 44f832a6-
Delete for volume 793235c6-
ERROR: Unable to delete any of specified volumes.
Although the volumes are there:
jgriffith@trusty ~ :( $ cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 44f832a6-
| 793235c6-
+------
Problem is that these volumes are STUCK in migration_
Changed in cinder: | |
assignee: | nobody → Liusheng (liusheng) |
Changed in cinder: | |
assignee: | Liusheng (liusheng) → nobody |
milestone: | kilo-1 → kilo-2 |
tags: | removed: icehouse-backport-potential juno-backport-potential |
Changed in cinder: | |
status: | In Progress → New |
milestone: | kilo-2 → kilo-3 |
milestone: | kilo-3 → none |
Changed in cinder: | |
assignee: | nobody → zwei (suifeng20) |
tags: | added: api |
Yuck