QuantumManager can't delete ports under load
Bug #926282 reported by
Matt Dietz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Under heavy load, and due to the way it is currently coded, quantum will frequently fail to deallocate ports on the switch. The solution is to ignore a failure to find a port by attachment, and simply issue a delete call for the port directly.
| Changed in nova: | |
| assignee: | nobody → Matt Dietz (cerberus) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
Revision history for this message
| Thierry Carrez (ttx) wrote | #2 |
| Changed in nova: | |
| assignee: | Matt Dietz (cerberus) → nobody |
| importance: | Undecided → Medium |
| status: | In Progress → Confirmed |
Revision history for this message
| Joe Gordon (jogo) wrote | #3 |
| Changed in nova: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/