Bug 1296501 - Retype a volume is failed with "Could not find a host for volume..."
Summary: Retype a volume is failed with "Could not find a host for volume..."
Keywords:
Status: CLOSED DUPLICATE of bug 1296502
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Eric Harney
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-07 11:51 UTC by lkuchlan
Modified: 2016-04-26 19:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-07 13:54:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs (14.96 MB, application/x-tar)
2016-01-07 11:51 UTC, lkuchlan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1531828 0 None None None 2016-01-07 11:57:05 UTC

Description lkuchlan 2016-01-07 11:51:41 UTC
Created attachment 1112423 [details]
logs

Description of problem:
Retype a volume without using "--migration-policy" optional argument is failed  with "Could not find a host for volume...", however when using this optional argument the operation succeed 
Another issue is that there is not an indication to the failure from CLI 

* I used 2 Netapp-nfs as back ends 

Version-Release number of selected component (if applicable):
openstack-cinder-2014.2.3-11.el7ost.noarch
python-cinder-2014.2.3-11.el7ost.noarch
python-cinderclient-1.1.1-1.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Retype a volume to a new back end without using the optional argument: "--migration-policy"

Actual results:
Retype a volume is failed with "Could not find a host for volume..."
There is not an indication to the failure from CLI  

Expected results:
The migration should also succeed, while not using "--migration-policy" optional argument
If the migration has failed should be an indication to the failure from CLI

Comment 2 Sean Cohen 2016-01-07 13:54:50 UTC

*** This bug has been marked as a duplicate of bug 1296502 ***


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