PLUMgrid plugin needs to handle concurrent API calls with locks
Bug #1250714 reported by
Edgar Magana
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Invalid
|
Low
|
Fawad Khaliq | ||
Bug Description
PLUMgrid plugins needs to handle concurrent API calls with a locking state. When multiple concurrent API calls are executed faster that what the PLUMgrid director processes them, some API calls will be stuck at the DB level and failing as a consequence.
| Changed in neutron: | |
| assignee: | nobody → Fawad Khaliq (fawad) |
| status: | New → Confirmed |
| Changed in neutron: | |
| status: | Confirmed → In Progress |
| Changed in neutron: | |
| status: | In Progress → New |
| tags: | added: plumgrid |
| Changed in neutron: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in neutron: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Fawad Khaliq (fawadkhaliq) wrote | #1 |
| Changed in neutron: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
marking it as invalid. this is not needed. locking was certainly one way and I have decided to have a better implementation as part of networking-