Random Bad Request Responses from Cinder API calls

Bug #1383771 reported by John Griffith
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Wishlist
Unassigned

Bug Description

Randomly receive 400 responses from Cinder API when trying to do things like delete volumes.

jgriffith@trusty ~ $ cinder delete 44f832a6-f759-4d69-b608-7b2579bc8e41 793235c6-93fb-4a44-8d37-1f89ee2e5b09
Delete for volume 44f832a6-f759-4d69-b608-7b2579bc8e41 failed: Bad Request (HTTP 400) (Request-ID: req-168c53e1-49b3-4b63-aac6-acc0f082f266)
Delete for volume 793235c6-93fb-4a44-8d37-1f89ee2e5b09 failed: Bad Request (HTTP 400) (Request-ID: req-0eea913f-cf2d-4756-ba0c-4611c9231581)
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-f759-4d69-b608-7b2579bc8e41 | available | None | 1 | foo | false | |
| 793235c6-93fb-4a44-8d37-1f89ee2e5b09 | available | None | 1 | foo | false | |
+--------------------------------------+-----------+------+------+-------------+----------+-------------+

Problem is that these volumes are STUCK in migration_status=completing and essentialy locked. There's no indication available of this other than going into the database and inspecting things.

Tags: api Edit Tag help
Revision history for this message
Duncan Thomas (duncan-thomas) wrote :

Yuck

Revision history for this message
Liusheng (liusheng) wrote :
Changed in cinder:
status: Triaged → In Progress
Mike Perez (thingee)
Changed in cinder:
assignee: nobody → Liusheng (liusheng)
Revision history for this message
Rushi Agrawal (rushiagr) wrote :

Just for info, the oslo patch has been merged. Please close this bug if the problems are no more visible. I'm not very sure the oslo patch solves everything, so..

Mike Perez (thingee)
Changed in cinder:
assignee: Liusheng (liusheng) → nobody
milestone: kilo-1 → kilo-2
Mike Perez (thingee)
tags: removed: icehouse-backport-potential juno-backport-potential
Changed in cinder:
status: In Progress → New
milestone: kilo-2 → kilo-3
milestone: kilo-3 → none
Revision history for this message
Praveen N (praveenn) wrote :

Just for information; there are much discussions on ask.openstack.org about the issues concerning
cinder delete $volumeid

Revision history for this message
NidhiMittalHada (nidhimittal19) wrote :

HI All,

I tested this bug in
stack@controller:~/devstack$ openstack --version
openstack 1.2.0

when a volume is being migrated ..
stack@controller:~/devstack$ cinder show 3ee38bf8-9982-4181-a78e-17d522ffd335

+---------------------------------------+--------------------------------------+
| Property | Value |
+---------------------------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2015-05-11T15:26:47.000000 |
| display_description | First Test volume |
| display_name | volume1 |
| encrypted | False |
| id | 3ee38bf8-9982-4181-a78e-17d522ffd335 |
| metadata | {} |
| multiattach | false |
| os-vol-host-attr:host | controller@lvmdriver-1#GOLD_BKEND |
| os-vol-mig-status-attr:migstat | migrating |>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | eeeb98b1ea5b4caca29b515696f53f62 |
| os-volume-replication:driver_data | None |
| os-volume-replication:extended_status | None |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| volume_type | None |
+---------------------------------------+--------------------------------------+

stack@controller:~/devstack$ cinder delete 3ee38bf8-9982-4181-a78e-17d522ffd335

Delete for volume 3ee38bf8-9982-4181-a78e-17d522ffd335 failed: Invalid volume: Volume cannot be deleted while migrating (HTTP 400) (Request-ID: req-47552db4-4acc-41b0-96df-79f87a8436c9)
ERROR: Unable to delete any of the specified volumes.

Which is a clear indication that volume can not be deleted as its in migrating state.

Hence this bug can be closed.

zwei (suifeng20)
Changed in cinder:
assignee: nobody → zwei (suifeng20)
Revision history for this message
Duncan Thomas (duncan-thomas) wrote :

It would be nice if the delete caused the migration to be cancelled - there's no point continuing to do work on a volume that is no longer wanted

Changed in cinder:
importance: High → Wishlist
Revision history for this message
Duncan Thomas (duncan-thomas) wrote :

Changed to wishlist since the error is now sensible, and the change to make the delete cancel the migration is a feature enhancement

Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Owner Expired

Unassigning due to no activity.

Changed in cinder:
assignee: zwei (suifeng20) → nobody
tags: added: api
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers