Hyper-V: vhd config drive images are not migrated
Bug #1619602 reported by
Lucian Petrut
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Lucian Petrut | ||
Newton |
Fix Committed
|
Medium
|
Matt Riedemann | ||
compute-hyperv |
Fix Released
|
Undecided
|
Unassigned |
Bug 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:/
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:/
The Hyper-V driver should not skip moving the config drive image.
affects: | os-win → nova |
description: | updated |
Changed in nova: | |
importance: | Undecided → High |
assignee: | nobody → Lucian Petrut (petrutlucian94) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/364829 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=2dd231cff19 9bd75bcd3d1031a 9ff0a1a82ec1cb
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2dd231cff199bd7 5bcd3d1031a9ff0 a1a82ec1cb
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
Closes-Bug: #1619602