HyperV: ensure config drives are copied as well during resizes
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.
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.
This change addresses the issue, removing the check that was
preventing the config drive from being copied.
Change-Id: I8cd42bed4515f4f75c92e595c4d8b847b16058dd
Closes-Bug: #1619602
(cherry picked from commit 2dd231cff199bd75bcd3d1031a9ff0a1a82ec1cb)
Reviewed: https:/ /review. openstack. org/379817 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=d39f4c8e901 b6247bd043d17b3 24e17833235ddc
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit d39f4c8e901b624 7bd043d17b324e1 7833235ddc
Author: Lucian Petrut <email address hidden>
Date: Fri Sep 2 13:39:29 2016 +0300
HyperV: ensure config drives are copied as well during resizes
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.
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.
This change addresses the issue, removing the check that was
preventing the config drive from being copied.
Change-Id: I8cd42bed4515f4 f75c92e595c4d8b 847b16058dd 5bcd3d1031a9ff0 a1a82ec1cb)
Closes-Bug: #1619602
(cherry picked from commit 2dd231cff199bd7