Bug 1928458 - Live migration of attached encrypted volume isn't supported due to Nova limitations
Summary: Live migration of attached encrypted volume isn't supported due to Nova limit...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Ian Frangs
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-14 08:28 UTC by Tzach Shefi
Modified: 2024-08-26 12:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-08-26 12:59:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-6274 0 None None None 2022-03-14 09:33:23 UTC

Description Tzach Shefi 2021-02-14 08:28:13 UTC
Description of problem: A recent 16.1.4 Cinder RFE bz1888672, added the option to live migrate attached volume from ceph to none ceph, a second related RFE bz1888674 does vise versa Ceph to none Ceph. 

While verifying these two I had stumbled upon a Nova limitation, 
https://bugzilla.redhat.com/show_bug.cgi?id=1926761#c4


If I understand correctly migration(retype) of attached encrypted volumes, isn't supported due to Nova limitation. This needs to be documented, I'm not sure where if in general storage or with relation to the two new RFEs. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Mikey Ariel 2024-08-26 12:59:50 UTC
This bug has been closed as EOL because it was submitted for an unsupported RHOSP version. If you believe this bug applies to supported RHOSP versions, please re-open and change the version accordingly, and provide a comment telling us why this bug is important to you with a link to your active support case. Thank you for your cooperation.


Note You need to log in before you can comment on or make changes to this bug.