yahoo-eng-team team mailing list archive

[Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>]

Did a resize, configdrive is attached. Looking through the code,  this
should not be an issue, the config drive is attached on finish_migration
(also called in case of a cold resize): [1]. This is included even in
Kilo. The only reason why the instance wouldn't have the config drive
attached is if it isn't required by the instance. Even then, there's the
config option force_config_drive that can be set to True. Even if there
is no config drive, metadata can still be fetched through the network.
Reopen if I'm wrong in any way.

@Li Wei, that's a bit strange. It is unrelated to the config drive
though. There might a couple of reason why that happened: the neutron
dhcp server didn't respond, or network issues, or the neutron-hyperv-
agent was dead when you performed the resize, thus, the neutron ports
were not bound to the VM's NICs.

[1]
https://github.com/openstack/nova/blob/master/nova/virt/hyperv/migrationops.py#L295

** Changed in: nova
       Status: Confirmed => Invalid

-- 
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/1301368

Title:
  Hyper-V configdrive is not atatched after resizing an instance

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  The following bug fix takes care of copying the configdrive to the
  resize target, but it does not attach it to the instance.
  https://bugs.launchpad.net/nova/+bug/1250324

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1301368/+subscriptions