Hash ring is stale after new conductor added
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Critical
|
Jim Rollenhagen |
Bug Description
A previous commit ( https:/
To reproduce:
* Spin up an API service, make some request that should go to a conductor (e.g. node-update). Observe expected behavior of "conductor not found that supports driver" or similar.
* Start a conductor service loaded with the driver for that node.
* Make the same node-update request. Observe erroneous behavior of "conductor not found that supports driver" or similar.
* Restart the API service. Make the same node-update request. Observe expected success.
Changed in ironic: | |
assignee: | nobody → Jim Rollenhagen (jim-rollenhagen) |
status: | New → In Progress |
Changed in ironic: | |
importance: | Undecided → Critical |
tags: | added: juno-rc-potential |
Changed in ironic: | |
milestone: | none → juno-rc2 |
Changed in ironic: | |
milestone: | juno-rc2 → 2014.2 |
Confirmed.
This one is my fault - amongst the various patches to fix the hash ring, I forgot to add a reset() call. Thanks for catching this, Jim!