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: Low => 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/1394219

Title:
  Failed to deploy new instance that server group on failed host

Status in OpenStack Compute (nova):
  Expired

Bug description:
  when the host is down/disable, for deploying instance that belongs to
  server group with affinity policy and other instances with same server
  group on the down/disable host, the scheduling will fail. Because
  scheduler is trying to find same host for the new instance.

  This is also for after we honors the server group when evacuate, if
  the instance is in server group with affinity can't be evacuated.

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