Bug 1309591 - Volume retype fails if volume's current type is None
Summary: Volume retype fails if volume's current type is None
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 9.0 (Mitaka)
Assignee: Tom Barron
QA Contact: nlevinki
Depends On:
TreeView+ depends on / blocked
Reported: 2016-02-18 08:32 UTC by Sergey Gotliv
Modified: 2017-02-26 21:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-04-03 10:53:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Launchpad 1547546 None None None 2016-02-19 15:23:58 UTC
OpenStack gerrit 282579 None None None 2016-02-20 16:28:20 UTC
Red Hat Knowledge Base (Solution) 2460451 None None None 2017-02-26 21:41:56 UTC

Description Sergey Gotliv 2016-02-18 08:32:07 UTC
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 1 Sergey Gotliv 2016-04-03 10:53:46 UTC
The patch is merged for Mitaka upstream.

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