Previously, volume migrations were generally not successful under a variety of circumstances. This was a result of vhost filtering verifying source host availability, rather than the destination host. In addition, the LVMBrick instance creation failed due to missing arguments.
With this update, Brick instance creation passes the expected arguments in their expected positions, and host filtering has been corrected.
Created attachment 830204[details]
the cinder logs
Description of problem:
while trying to validate an RFE about volume migration, https://blueprints.launchpad.net/cinder/+spec/volume-migration , the feature didn't function.
It failed to move the different volumes from one backend to another:
1. lvm to nfs
2. nfs to lvm
3. lvm to lvm
Version-Release number of selected component (if applicable):
openstack-cinder-2013.2-2.el6ost.noarch
python-cinderclient-1.0.6-2.el6ost.noarch
python-cinder-2013.2-2.el6ost.noarch
Red Hat Enterprise Linux Server release 6.5 (Santiago)
How reproducible:
evertime
Steps to Reproduce:
1. Configure the Cinder to run with multiple backend (with different types of backends). follow the documentation: http://docs.openstack.org/admin-guide-cloud/content//managing-volumes.html
2. migrate one of the volumes to the other backend.
3.
Actual results:
the volume failed to migrate
Expected results:
the volume have migrated
Additional info:
the log are attached.
Could you please share the exact procedure you're following to reproduce this bug?
Scheduler's log mentions there's no valid host to migrate the volume to.
in addition I've ran all the commands from the nova machine and not locally from the cinder machine.
The entire topology is:
Machine 1: Nova, Neutron, Keystone, Swift.
Machine 2: Cinder.
Machine 3: Glance.
When I run the migrate command from the Cinder machine it works.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2013-1859.html