Bug 1956366 - [RHOSP 16.2][Backport] Fix for PowerFlex/vxflex volume type conversion
Summary: [RHOSP 16.2][Backport] Fix for PowerFlex/vxflex volume type conversion
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 16.2 (Train on RHEL 8.4)
Assignee: Pablo Caruana
QA Contact: Tzach Shefi
Andy Stillman
URL:
Whiteboard:
Depends On: 1883326
Blocks: 1824852 1861408
TreeView+ depends on / blocked
 
Reported: 2021-05-03 14:34 UTC by arkady kanevsky
Modified: 2022-08-23 10:43 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1883326
Environment:
Last Closed: 2021-05-24 18:20:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 754785 0 None MERGED Fix PowerFlex volume type conversion 2021-05-10 21:12:54 UTC
Red Hat Issue Tracker OSP-3561 0 None None None 2022-08-23 10:43:00 UTC

Comment 2 arkady kanevsky 2021-05-03 14:37:44 UTC 
Duplicate for RHOSP 16.2
Comment 4 arkady kanevsky 2021-05-10 18:41:40 UTC 
https://review.opendev.org/c/openstack/cinder/+/754785 finally landed upstream.
Dell will backport it all the way to Train if upstream community will allow it.
Hope we can land it in GA so we can use it for re-cert.
Comment 5 Pablo Caruana 2021-05-13 15:39:35 UTC 
+++ This bug was initially created as a clone of Bug #1883326 +++
Fix PowerFlex volume type conversion

Fix bug with PowerFlex storage-assisted volume migration when volume migration was performed without conversion of volume type in cases where it should have been converted to/from thin/thick provisioned.
Comment 6 arkady kanevsky 2021-05-17 14:08:50 UTC 
Suggest we target this functionality to RHOSP-17 since volume retype is used for volume migration that is targeted for 17.0
Thus I suggest we close this BZ and target Bug #1883326 to 17.
Note You need to log in before you can comment on or make changes to this bug.