dd12492f32
Managing a volume to an encrypted volume type should not be allowed. One reason is that there is no way for an operator to specify an encryption key ID for the volume. Another is that we already don't allow a volume of an encrypted type to be un-managed, so this change will be symmetric. Also update and correct the api-ref for this call. Co-authored-by: xuan <xuanyd@outlook.com> Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com> Change-Id: Ic2da41f3962c1108f974aca952bce3da6d6ac277 Closes-bug: #1944577 (cherry picked from commit8088dc9580) change: cinder/tests/unit/api/contrib/test_volume_manage.py - used a feature of unittest.mock that was introduced in py38; rewritten to be compatible with py36 (cherry picked from commit9c1aa92b95)
9 lines
355 B
YAML
9 lines
355 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #1944577 <https://bugs.launchpad.net/cinder/+bug/1944577>`_:
|
|
Managing a volume to an encrypted type was never a good idea because
|
|
there was no way to specify an encryption key ID so that the volume
|
|
could be used. Requests to manage a volume to an encrypted volume
|
|
type now result in an invalid request response.
|