Allocations records aren't removed after rescheduling
Bug #1712718 reported by
Alex Xu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann | ||
Pike |
Fix Committed
|
High
|
Matt Riedemann |
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.
description: | updated |
tags: | added: placement |
tags: | added: scheduler |
Changed in nova: | |
assignee: | nobody → Alex Xu (xuhj) |
status: | New → In Progress |
description: | updated |
tags: | added: pike-rc-potential |
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
assignee: | Alex Xu (xuhj) → Matt Riedemann (mriedem) |
To post a comment you must log in.
There ia functional test for this bug https:/ /review. openstack. org/#/c/ 496995/