Buddies,

I can migration nova instance across available zones with the command below. Suppose instance is in AZ1 and host is in AZ2.

nova --os-compute-api-version 2.67 live-migration --force [--block-migrate] <server> [<host>]

After migration, the instance’s available zone is changed to AZ2.

However, the available zone information in request_specs was not changed.

So next time when trying to migrate the instance without specifying a target, the migration target will be selected through nova scheduler, by the availability zone value (AZ1) saved in request_specs. This caused some error.

Is this an expected behavior ?

Yingji.