allocation duplicate after host-evacuation
Bug #2087761 reported by
Holger HUO
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| placement |
New
|
Undecided
|
Unassigned | ||
Bug Description
After executing `nova host-evacuate --target_host new_node failed_node`, there is a duplicate resource allocation on both failed_node and the new_node.
Steps to reproduce:
1. evacuate all instances with `nova host-evacuate --target_host new_node failed_node`
2. check project allocations from either `/usages?
Result: There are two identical records with only resource_
Expected Result: allocation from failed host getting released.
Maybe some race condition in placement, any ideas on further debug?
To post a comment you must log in.
Other information:
1. (Maybe related) we executed `nova host-evacuate --target_host new_node failed_node` twice (`nova host-evacuate --target_host new_node1 failed_node` and `nova host-evacuate --target_host new_node2 failed_node`). The first attempt had no effect for unknown reasons.
2. Another project has two generations of consumer (generation 1 and 4), which also caused allocation to go over actual resource usage. According to the api-ref/src, shouldn't each record has only one generation?