manila/releasenotes/notes/bug-1688620-netapp-migration-cancelation-fb913131eb8eb82a.yaml
dtapia a0dd86a987 [NetApp] Updating the release note for bugfix 1688620
This patch update the release note of the bugfix for the bug 1688620
explaining better about the added configuration option and its use.

Related-Bug: #1688620
Change-Id: Idf9730bfc9604f906b10e58f5b767b4030d8f0db
2020-06-16 14:28:36 +00:00

21 lines
1.0 KiB
YAML

---
fixes:
- |
NetApp ONTAP share delete operation can fail sometimes when is triggered
immediately after migration cancelation on a overloaded NetApp backend.
Canceling an ongoing migration is an asynchronous operation on an
ONTAP storage system.
Now the NetApp driver checks if the asynchronous API has ended its
operation before reporting migration cancelation success. If the operation
of the asynchronous API did not end within the specified timeout, the
``migration cancel`` cancel operation will be considered unsuccessful.
To do so, a new configuration option ``netapp_migration_cancel_timeout``
has been added.
upgrade:
- |
The configuration option ``netapp_migration_cancel_timeout`` can be
specified in the NetApp backend section to redefine the amount of time
that the NetApp driver must attempt to wait on the asynchronous
operation to cancel an ongoing migration. This option is set to 3600
seconds by default, which is sufficient time in most cases.