Bug 1296501
| Summary: | Retype a volume is failed with "Could not find a host for volume..." | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | lkuchlan <lkuchlan> | ||||
| Component: | openstack-cinder | Assignee: | Eric Harney <eharney> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | nlevinki <nlevinki> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0 (Juno) | CC: | eharney, scohen, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 8.0 (Liberty) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-01-07 13:54:50 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 1296502 *** |
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