Cannot specify target host with 'openstack server migrate --block-migration'

Bug #1634605 reported by Andrew Bogott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-openstackclient
New
Undecided
Unassigned

Bug Description

On a shared storage system, I can do

openstack server migrate --live <hostname> <server>

If I don't have shared storage and want to do block migrate, I can do

openstack server migrate --block-migrate <server>

But --block-migrate doesn't take a <hostname> argument. The underlying API supports a destination host, and the old 'nova migrate' command also supported it:

nova live-migration --block-migrate <server> [<host>]

Revision history for this message
Steve Martinelli (stevemar) wrote :

the --live <host> option should work for both --block-migration and --shared-migration, and will pass both along to novaclient. i'm wondering if this is related to the recent fix [1]

[1] https://github.com/openstack/python-openstackclient/commit/694a24c3093f5b2595b63ccf988da7972e532084

Revision history for this message
Andrew Bogott (andrewbogott) wrote :

It may indeed be fixed by that patch, I will try to test. But for now...

$ openstack server migrate --block-migration 1bc4cf77-2f5e-4144-9e65-c5a5e44f53bf --live labvirt1014
labvirt1011 is not on shared storage: Live migration can not be used without shared storage except a booted from volume VM which does not have a local disk. (HTTP 400) (Request-ID: req-e8bc5009-7c55-431d-8951-b7c53a58a12a)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.