Unmanaging encrypted volumes is problematic because
unmanage assumes that you will be able to manage the
volume again for later use, but, we have no mechanism
currently to keep track of the encryption key which
would be required for using an encrypted volume again.
While this may work out ok when using the conf_key
manager, this patch does not distinguish between conf_key
and barbican deployments.
* The Ocata backport skips the async error message for
this event due to refactoring of the messages system,
to minimize risk.
Closes-Bug: #1731518
Change-Id: I7506fa36962404c80f1cc9c6370693728e5393a7
(cherry picked from commit de584713d9)
Conflicts:
cinder/volume/api.py
(cherry picked from commit 30ca90ffcc)
Conflicts:
cinder/message/message_field.py
cinder/tests/unit/api/contrib/test_volume_unmanage.py
cinder/tests/unit/volume/test_volume.py
dd727943d0