yahoo-eng-team team mailing list archive

[Claudiu Belu <cbelu@xxxxxxxxxxxxxxxxxxxxxx>]

** Also 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/1556189

Title:
  Hyper-V: destroying an instance can fail, having in-use files

Status in compute-hyperv:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  In some cases, destroying an instance can fail, having the instance
  log files still in-use.

  This can happen in the following scenario:
  1. The vm is powered on
  2. The vm is requested to be destroyed shortly after (less than a few seconds). This driver will now attempt to stop the serial console workers, but none exist yet
  3. The instance power on event callback is run, spawning the serial console workers
  4. The instance is powered off as the destroy operation continues. The serial console workers are not explicitly stopped now. The instance serial port named pipe should be stopped now, which will cause the serial workers to stop themselves shortly after, but before this happens, the driver attempts to delete the instance files, while the console logs are still in use, which will fail.

  Trace: http://paste.openstack.org/show/490196/

  The easiest way to avoid this issue would be to simply retry deleting
  the instance files if this fails, also ensuring again that the console
  workers are stopped. Note that this is quite unlikely to happen in a
  real life deployment.

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