yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #66912
[Bug 1712718] Re: Allocations records aren't removed after rescheduling
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova/pike
Importance: Undecided => High
--
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):
In Progress
Status in OpenStack Compute (nova) pike series:
Confirmed
Bug description:
When all the nodes are Pike release, 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
References