yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  nova evacuate --on-shared-storage doesn't check actual vm state

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Currently, when we evacuate an instance, evacuation mechanism checks
  only if nova-compute is down on failed host. If nova compute fails and
  vm's are still alive, we still can perform evacuation, but 2 separate
  vms will write to same disk, and that might break data integrity on
  disk. There should be better host health monitoring, which will give
  us better hint if we can perform safe evacuation.

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