danielarthurt 1199489d99 [NetApp] Fix falsely report migration cancelation success ... NetApp ONTAP share delete operation can fail sometimes when is triggered immediately after migration cancelation on a overloaded NetApp backend. Migration cancelation invokes "abort_volume_move" which is an asynchronous API. If share delete operation is requested immediately after call the former API, it fails because the "abort_volume_move" is still in progress. Now NetApp cDOT driver checks, for a period of time, if the ``volume-move-abort`` operation has ended before report migration cancelation success. This patch squash the following commit that improves the release note for this fix: [NetApp] Updating the release note for bugfix 1688620 (cherry picked from commit a0dd86a987) Change-Id: I76e11fef27c9723f019cfdfdc6ea86878db78776 Closes-Bug: #1688620 (cherry picked from commit 0ee4140823) (cherry picked from commit 71c3a08ead) (cherry picked from commit c915918f3c)		2020-07-29 10:17:53 +00:00
..
__init__.py	Manila NetApp cDOT driver refactoring	2015-02-10 12:30:24 +00:00
data_motion.py	NetApp cDOT: Add support for QoS/throughput ceilings	2017-07-23 16:44:08 -04:00
drv_multi_svm.py	[NetApp] Add manage/unmanage of share servers	2019-03-05 19:18:01 +00:00
drv_single_svm.py	[NetApp] Add manage/unmanage of share servers	2019-03-05 19:18:01 +00:00
lib_base.py	[NetApp] Fix falsely report migration cancelation success	2020-07-29 10:17:53 +00:00
lib_multi_svm.py	[NetApp] Fix race condition issues on vserver deletion	2019-06-24 18:50:08 +00:00
lib_single_svm.py	Simplify the way drivers report support for ipv6	2017-12-06 15:21:53 +00:00
performance.py	Remove log translations in share and share_group 4/5	2017-03-31 10:20:11 +08:00