Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1361271 - Backport for OSP 5: Volume retype fails if volume's current type is None
Summary: Backport for OSP 5: Volume retype fails if volume's current type is None
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 7.0 (Kilo)
Assignee: Eric Harney
QA Contact: nlevinki
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-28 16:22 UTC by Andreas Karis
Modified: 2019-02-17 12:23 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-04-04 14:37:57 UTC
Target Upstream Version:
tshefi: automate_bug-

Attachments (Terms of Use)

Description Andreas Karis 2016-07-28 16:22:51 UTC
Description of problem:
Please backport to OSP 5.

Description of problem:

Cinder retype command fails if volume doesn't have a source type.

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

We discovered it in OSP 5.0 but it seems that this issue can 
happen even in the master branch.

How reproducible:
100% on OSP 5.0

Steps to Reproduce:
1. Make sure that cinder.conf doesn't specify a default volume type
2. Create volume without specifying volume type
3. Retype this volume to the new type

Actual results:

Retype fails

Expected results:

Volume should get retyped

Additional info:

1. Configuring a default volume type in cinder.conf resolves that issue.
2. Use cinder migrate instead of retype if all you want is to move volume between different backends.

Comment 9 Tzach Shefi 2018-09-23 19:39:18 UTC
Nothing to automate/test here as it wasn't backported. 
Also while we are at it I just verified on OSP14 OSPD now deploys a default backend as see here:

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