yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

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

Title:
  Exists notification sent even if rescue fails

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When a rescue operation is initiated in Nova, a partial-period .exists
  event is emitted to capture instance runtime, etc for the period
  before the rescue.  Currently, this occurs just before the actual
  rescue operation is kicked off on the hypervisor.

  If the rescue operation is interrupted by another user operation, such
  as a delete or rebuild, before it finishes, then the rescue will not
  complete, and the instance's launched_at time will not be reset. This
  will result in the instance runtime for the partial .exists, and the
  end-of day .exists overlapping.

  To fix this, the notify_usage_exists() call in ComputeManager's
  rescue_instance method should be moved to after the driver.rescue()
  call completes, just before the instance update that changes the
  launched_at timestamp. This will prevent the extra .exists from being
  emitted if the rescue is interrupted, and the launched_at is not
  changed.

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