yahoo-eng-team team mailing list archive

[Alex Xu <soulxu@xxxxxxxxx>]

Public bug reported:

The allocations records aren't removed from the destination host which
failed to boot up the instance, after the instance are rescheduled in
another host, the allocation records for the failed host still exists.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: placement scheduler

** Description changed:

- The allocations records are removed from the destination host which
- failed to boot up instance, after the instance are rescheduled in
- another host, the allcoations records for the failed host still exists.
+ The allocations records aren't removed from the destination host which
+ failed to boot up the instance, after the instance are rescheduled in
+ another host, the allocation records for the failed host still exists.

** Tags added: placement

** Tags added: scheduler

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

Title:
  Allocations records aren't removed after rescheduling

Status in OpenStack Compute (nova):
  New

Bug description:
  The allocations records aren't removed from the destination host which
  failed to boot up the instance, after the instance are rescheduled in
  another host, the allocation records for the failed host still exists.

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