Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/volume-migration. Description: Cinder now has the ability to migrate a volume, This functionality should be exposed through Horizon. Specification URL (additional information): None
Failed QA ========= python-django-horizon-8.0.0-10.el7ost.noarch openstack-dashboard-8.0.0-10.el7ost.noarch python-cinder-7.0.1-5.el7ost.noarch openstack-cinder-7.0.1-5.el7ost.noarch python-cinderclient-1.4.0-1.el7ost.noarch 1. Create two Netapp-NFS backends Netapp1 and Netapp2 2. Create volume on Netapp1 3. Admin tab go to : System --> Volumes --> Volumes 4. On the created volume click Actions --> Migrate Volume 5. On Migrate Volume dialog select Destination host Netapp2 and click Migrate Actual results: =============== From Horizon ----> Error: Failed to migrate volume. ----------------------------------- /var/log/horizon/horizon.log: WARNING horizon.exceptions Recoverable error: migrate_volume() takes exactly 5 arguments (4 given) ----------------------------------- /var/log/cinder/scheduler.log: ERROR cinder.scheduler.manager [req-8667209e-8636-419f-b7c4-2c6a444bf8f2 895a2cab60e449939bc1764458f305a3 3a85e4a722e64171be1f495f3c47ccc8 - - -] Failed to schedule_migrate_volume_to_host: No valid host was f ound. Cannot place volume 823687ab-965e-40b9-9e14-1b9639786c4e on overcloud-controller-0.localdomain@Netapp2 -------------------------------------- Additional information: https://bugzilla.redhat.com/show_bug.cgi?id=1296502
@Itxaka what did you find when looking at the FailedQA results? Moving bug back to MODIFIED until we get some feedback as to why it should be moved to ON_QA again.
@Jon Can confirm that this is not fixed, even on master upstream. There is a bug for this but seems to be ignored, I will take care of it.
The patch is merged upstream to master, I did a backport to Liberty as well and waiting on that.
Verifiied ========= python-django-horizon-8.0.1-1.el7ost.noarch
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. https://rhn.redhat.com/errata/RHEA-2016-0603.html