← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1388213] [NEW] Possible to crash nova compute node via deletion of a resizing instance (timing bug)

 

Public bug reported:

NOTE: tests run against devstack install on Ubuntu 14.04
tests conducted via randomized testing, no definitive test case produced yet, but have repeated this several times.

It appears that deleting a resizing instance can cause the nova compute node to crash with the following error / traceback:
(more detailed output below)
screen-n-cpu.2014-10-31-081111.log:354289:2014-10-31 11:01:58.093 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 896, in createWithFlags
screen-n-cpu.2014-10-31-081111.log:354290:2014-10-31 11:01:58.093 TRACE oslo.messaging.rpc.dispatcher     if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
screen-n-cpu.2014-10-31-081111.log:354291:2014-10-31 11:01:58.093 TRACE oslo.messaging.rpc.dispatcher libvirtError: Domain not found: no domain with matching uuid '2aadc976-951e-47d6-bb20-9e071a6a89a9' (instance-00000360)

When this is triggered, the compute node will crash and all instances will end up in ERROR state.
Have not perfected the timing parameters, but will provide output from two runs below.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Possible to crash nova compute node via deletion of a resizing
  instance (timing bug)

Status in OpenStack Compute (Nova):
  New

Bug description:
  NOTE: tests run against devstack install on Ubuntu 14.04
  tests conducted via randomized testing, no definitive test case produced yet, but have repeated this several times.

  It appears that deleting a resizing instance can cause the nova compute node to crash with the following error / traceback:
  (more detailed output below)
  screen-n-cpu.2014-10-31-081111.log:354289:2014-10-31 11:01:58.093 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 896, in createWithFlags
  screen-n-cpu.2014-10-31-081111.log:354290:2014-10-31 11:01:58.093 TRACE oslo.messaging.rpc.dispatcher     if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
  screen-n-cpu.2014-10-31-081111.log:354291:2014-10-31 11:01:58.093 TRACE oslo.messaging.rpc.dispatcher libvirtError: Domain not found: no domain with matching uuid '2aadc976-951e-47d6-bb20-9e071a6a89a9' (instance-00000360)

  When this is triggered, the compute node will crash and all instances will end up in ERROR state.
  Have not perfected the timing parameters, but will provide output from two runs below.

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


Follow ups

References