Concurrency issues with bulk access rule updates
Bug #1626249 reported by
Goutham Pacha Ravi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
Goutham Pacha Ravi | ||
Bug Description
This bug is spawned from https:/
Please see the discussion on https:/
Steps to reproduce:
When adding several rules by using a script like:
for i in `seq 1 100`; do manila access-allow share ip 10.0.0.$i; done
Eventually, the share instance access-rules-status gets changed to "updating multiple" on the API after the manager has already checked if the status is "updating multiple". Due to this error, the allow/deny APIs get stuck for this share instacce.
Revision history for this message
| Goutham Pacha Ravi (gouthamr) wrote | #1 |
| Changed in manila: | |
| importance: | Undecided → High |
| assignee: | nobody → Goutham Pacha Ravi (gouthamr) |
| milestone: | none → ocata-1 |
| tags: | added: api |
| Changed in manila: | |
| status: | New → In Progress |
| Changed in manila: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/
Changed in manila:
status: Confirmed → In Progress