NetApp cDOT driver reports migration cancelation was successful even if it wasn't

Bug #1688620 reported by Goutham Pacha Ravi on 2017-05-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Naresh Kumar Gunjalli

Bug Description

This is a hard to trigger bug, and probably easier to catch on a very busy NetApp cDOT back end:

* Configure the NetApp cDOT driver (DHSS True/False, doesn't matter)
* Create a share
    $ manila create nfs 1 --share-type gotonetapp --name myshare
* Start migration for the share

   $ manila migration-start myshare pool2000 --nondisruptive True --preserve-metadata True --preserve-snapshots True --writable True
* Cancel the migration
   $ manila migration-cancel myshare
* Delete the share as soon as it transitions to "available" state

   $ manila delete myshare

The deletion could fail with the following error in m-share :

"share_221a269a_f64a_4d3a_b91e_6217686b978e” in Vserver “vserver_eb31a90e" cannot be offlined because a volume move operation is in progress.

volume-move-trigger-abort is an asynchronous API. It will return with "passed"/success when invoked but the volume on the back end isn't ready for any further interaction yet.

Changed in manila:
importance: Undecided → Low
assignee: nobody → Goutham Pacha Ravi (gouthamr)
description: updated
tags: added: netapp
Changed in manila:
assignee: Goutham Pacha Ravi (gouthamr) → nobody
Tom Barron (tpb) on 2018-06-19
tags: added: driver migration
Jason Grosso (jgrosso) on 2019-03-22
Changed in manila:
assignee: nobody → Jason Grosso (jgrosso)
status: New → Triaged
Changed in manila:
assignee: Jason Grosso (jgrosso) → Naresh Kumar Gunjalli (nareshkumarg)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers