[cinder] retype command doesn't delete volume on solidfire

Bug #1609963 reported by Andrey Grebennikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Fix Released
High
Ivan Kolodyazhny
8.0.x
Fix Released
High
Ivan Kolodyazhny
9.x
Fix Released
High
Ivan Kolodyazhny

Bug Description

MOS8 with netapp nfs and solidfire (iscsi) backends for cinder.
Customer wants to execute volume retyping sometimes, and it turns out retyping works fine for netapp->solidfire, but has an issue with solidfire->netapp.
In this case the volume gets created on the netapp, the data is transferred, but the source volume never gets deleted on solidfire.

The log says:
2016-08-04 19:09:23.652 28961 ERROR cinder.volume.drivers.solidfire [req-b2cc5e26-06b4-454a-910a-c454155e81eb 79d85a14c1a34a758a747e668bafe10f 563d9b14b7a1464f9bfbfbc4cc4c49d5 - - -] Volume ID 9f2ee348-10be-4f33-
97a3-9dc18aab6486 was not found on the SolidFire Cluster while attempting delete_volume operation!
Which is wrong - the temporary volume ID is used in this case, not the original one.

In solidfire driver it is necessary to use "name_id" value from the volume object instead of "id".

tags: added: customer-found
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :
Changed in mos:
milestone: none → 8.0-updates
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :
tags: added: on-verification
Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Patch was verified on customer's environment

Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Move to Fix Released according to the previous comment #3.
Fix for 8.0 is available in MU3 updates.

tags: removed: on-verification
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

It is not clear how to verify the fix (steps to reproduce require some plugins), I've checked the code on my MOS 9.1 environment and fix is presented here, since the fix was tested on the customer env we marked this issue Fix Released for 9.1 and 10.0 releases as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.