yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

** Changed in: compute-hyperv
       Status: New => 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/1208301

Title:
  The VM will be destroyed on source host during resizing for Hyper-V

Status in compute-hyperv:
  Invalid
Status in OpenStack Compute (nova):
  Expired

Bug description:
  This defect is originally be found in the following scenario:

  1. Deploy one vm  A  with 100g disk and 1 cpu.
  2. Resize it with 2 cpu and 200g disk
  3. During resizing,  the host of vm is down (power off )
  4. restart the host

  After investigation, I found that in the method of
  migrate_disk_and_power_off of the migrationops, which is called by the
  Hyper-V driver, the VM gets removed as its last step.

  https://github.com/openstack/nova/blob/master/nova/virt/hyperv/driver.py
  https://github.com/openstack/nova/blob/master/nova/virt/hyperv/migrationops.py

  Compared with the same scenario in KVM, the previous case works, which
  means the VM being resized won't be removed and after the host is up
  again, the resize can resume.

  Since I am not familiar with the orginal design and don't know why
  Hyper-V handle resizing like this. So open this defect for tracking
  and discussion.

  One question I can propose here is: is there a standard behavior among
  the hypervisors for resizing? if yes, what is it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1208301/+subscriptions