Unable to import/manage an encrypted volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Medium
|
Unassigned |
Bug Description
We make use of one of the Cinder drivers so we can have our volumes on a Dell PowerVault storage device.
We use encrypted volumes, and we know that it is currently not possible to manage/import encrypted volumes.
(See: https:/
This means, if we have an encrypted volume from a previous OpenStack deployment, we cannot get this volume into Cinder in the new deployment.
We are forced to create a new volume, and copy the data.
We simply want to have the option of providing the LUKS encryption key that the encrypted volume uses, when importing/managing a volume.
One use case we would like is that this would probably let us use `cryptsetup` to create and prepopulate an encrypted volume, before OpenStack is even deployed. We have been able to use `cryptsetup open` to decrypt the encrypted volumes and access the data within.
But to be clear, if this only works/supported for encrypted volumes created by Cinder itself, that is fine.
description: | updated |
Changed in cinder: | |
importance: | Undecided → Medium |
tags: | added: encryption import volume |