yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #20483
[Bug 1321640] Re: [HyperV]: Config drive is not attached to instance after resized or migrated
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => juno-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1321640
Title:
[HyperV]: Config drive is not attached to instance after resized or
migrated
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
If we use config-drive (whether set --config-drive=true in boot
command or set force_config_drive=always in nova.conf), there is bug
for config-drive when resize or migrate instances on hyperv.
You can see from current nova codes:
https://github.com/openstack/nova/blob/master/nova/virt/hyperv/migrationops.py#L269
when finished migration, there is no code to attach configdrive.iso or configdrive.vhd to the resized instance. compared to boot instance (https://github.com/openstack/nova/blob/master/nova/virt/hyperv/vmops.py#L226). Although this commit https://review.openstack.org/#/c/55975/ handled coping configdrive to resized or migrated instance, there is no code to attach it after resized or migrated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1321640/+subscriptions
References