8a75d036f6
Our os-brick connector already handles the "keep track of which volume is attached for what reason" calls to storpool.spopenstack. However, we need to explicitly specify the access mode in initialize_connection() now, since our os-brick connector does not know how to divine it yet. (this will come later with the "attach snapshot" functionality) Incidentally, this fixes the "create an encrypted volume" flow, since our _attach_volume() implementation never actually returned a connector in the attachment info... Change-Id: I5da7ae04b87b4fd52a682a6545060e852174f6c8 Closes-Bug: #1939241
8 lines
270 B
YAML
8 lines
270 B
YAML
---
|
|
fixes:
|
|
- |
|
|
StorPool driver `bug #1939241
|
|
<https://bugs.launchpad.net/cinder/+bug/1939241>`_: Fixed the creation of
|
|
encrypted StorPool volumes by dropping the needlessly and incompletely
|
|
overridden `_attach_volume()` and `_detach_volume()` methods.
|