| 2016-09-02 10:41:56 |
Lucian Petrut |
description |
During cold migration, vhd config drive images are not copied over, on the wrong assumption that the instance is already configured and does not need the config drive.
There is an explicit check at the following location:
https://github.com/openstack/nova/blob/8f35bb321d26bd7d296c57f4188ec12fcde897c3/nova/virt/hyperv/migrationops.py#L75-L76
For this reason, migrating instances using vhd config drivers will fail, as there is a check ensuring that the config drive is present, if required:
https://github.com/openstack/nova/blob/8f35bb321d26bd7d296c57f4188ec12fcde897c3/nova/virt/hyperv/migrationops.py#L153-L163
The Hyper-V driver should not skip moving the config drive image. |
During cold migration, vhd config drive images are not copied over, on the wrong assumption that the instance is already configured and does not need the config drive.
There is an explicit check at the following location:
https://github.com/openstack/nova/blob/8f35bb321d26bd7d296c57f4188ec12fcde897c3/nova/virt/hyperv/migrationops.py#L75-L76
For this reason, migrating instances using vhd config drives will fail, as there is a check ensuring that the config drive is present, if required:
https://github.com/openstack/nova/blob/8f35bb321d26bd7d296c57f4188ec12fcde897c3/nova/virt/hyperv/migrationops.py#L153-L163
The Hyper-V driver should not skip moving the config drive image. |
|
