| 1 |
--- |
| 2 |
fixes: |
| 3 |
- | |
| 4 |
Dell PowerMax Driver `Bug #2045230 |
| 5 |
<https://bugs.launchpad.net/cinder/+bug/2045230>`_: Fixed |
| 6 |
the issue that Dell PowerMax SnapVx link fails as the linked device is not |
| 7 |
yet fully defined. |
| 8 |
|
| 9 |
Previously, the below operations could fail if the linked device was not |
| 10 |
yet fully defined at the time of the call. |
| 11 |
Now, when ``snapvx_unlink_symforce`` is enabled, those operations are not |
| 12 |
interrupted by not fully defined devices. |
| 13 |
|
| 14 |
By default, ``snapvx_unlink_symforce`` is ``False``. Use extreme caution |
| 15 |
with this option. If used when a link is copy in progress or when a restore |
| 16 |
is restore in progress, this will cause an incomplete copy and data on the |
| 17 |
copy target would not be usable. |
| 18 |
|
| 19 |
Impacted operations: |
| 20 |
|
| 21 |
* Clone a volume |
| 22 |
* Create a volume from a snapshot |
| 23 |
* Create volume snapshots |
| 24 |
* Delete volume snapshots |
| 25 |
* Revert volume to snapshot |
| 26 |
* Create generic volume group from source |
| 27 |
* Unmanage volumes |
| 28 |
upgrade: |
| 29 |
- | |
| 30 |
Dell PowerMax Driver: introduced a new configuration option, |
| 31 |
``snapvx_unlink_symforce``, to address Bug #2045230. See the Bug Fixes |
| 32 |
section for details. |