danielarthurt 826cbfa7ce [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) (cherry picked from commit 1199489d99) (cherry picked from commit b8fc8feb07)		2020-08-04 14:14:07 +00:00
..
dataontap	[NetApp] Fix falsely report migration cancelation success	2020-08-04 14:14:07 +00:00
__init__.py	Move driver unittest modules to proper place	2014-09-08 11:37:49 +03:00
fakes.py	Manila NetApp cDOT driver refactoring	2015-02-10 12:30:24 +00:00
test_common.py	Removed unnecessary setUp() calls in tests	2017-08-02 12:47:34 +00:00
test_utils.py	NetApp ONTAP: Add support for filtering API tracing	2017-09-20 16:01:33 -04:00