yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

long incomplete bug

** Tags removed: havana-backport-potential

** Summary changed:

- Instance status always being building after memory shortage error happen
+ HyperV: Instance status always being building after memory shortage error happen

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

** Changed in: nova
     Assignee: Matt Riedemann (mriedem) => (unassigned)

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

Title:
  HyperV: Instance status always being building after memory shortage
  error happen

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  TEST STEPS:
  1)  Try to use Automation tool to deploy 600 VMs. (Including resize and delete)
        (Using flavors of m1.small)
  2)  When we had deployed 427 VMs, the memory of compute node was shortage.
  3)  Time out occur.

  Expected result: Once the memory shortage was happened, the deploying should be stopped and openstack will show the ERROR status to user.
  Actual result: The status of the deploying is still BUILD and we can find the error message from the compute.log of compute node.

  we can find below message compute.log about the shortage of memory.

  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops HyperVException: WMI job failed with status 10. Error details: 'instance-000002aa' could not initialize.
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops Not enough memory in the system to start the virtual machine instance-000002aa. - 'instance-000002aa' could not initialize. (Virtual machine ID BAEB8C16-DBE5-488D-B55C-59543A8F0885)
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops Not enough memory in the system to start the virtual machine instance-000002aa with ram size 2048 megabytes. (Virtual machine ID BAEB8C16-DBE5-488D-B55C-59543A8F0885) - Error code: 32778
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops
  2013-05-29 01:07:20.289 ERROR nova.virt.hyperv.vmops [req-e2855532-03eb-484a-9b53-4c7a8cb37795 a6ab9c2b52554567b2c0281636398bfc aef9ae3aeace49a080d22e46295834b4] Failed to change vm state of instance-000002aa to 2
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops Traceback (most recent call last):
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops   File "C:\Program Files (x86)\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 184, in spawn
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops     self.power_on(instance)
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops   File "C:\Program Files (x86)\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 369, in power_on
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops     constants.HYPERV_VM_STATE_ENABLED)
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops   File "C:\Program Files (x86)\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py", line 380, in _set_vm_state
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops     raise vmutils.HyperVException(msg)
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops HyperVException: Failed to change vm state of instance-000002aa to 2
  2013-05-29 01:07:20.289 5600 TRACE nova.virt.hyperv.vmops
  2013-05-29 01:07:20.289 INFO nova.virt.hyperv.vmops [req-e2855532-03eb-484a-9b53-4c7a8cb37795 a6ab9c2b52554567b2c0281636398bfc aef9ae3aeace49a080d22e46295834b4] Got request to destroy instance: instance-000002aa
  2013-05-29 01:07:20.352 DEBUG nova.virt.hyperv.vmops [req-e2855532-03eb-484a-9b53-4c7a8cb37795 a6ab9c2b52554567b2c0281636398bfc aef9ae3aeace49a080d22e46295834b4] [instance: f82a4a9d-48a7-4361-8dbd-c906ca94b008] Power off instance power_off C:\Program Files (x86)\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\vmops.py:361

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