orphaned rule if inserted while policy under deletion
Bug #1622438 reported by
Eric K
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| congress |
Triaged
|
Medium
|
Eric K | ||
Bug Description
In multi-policy-engine scenario, if node 1 attempts to insert a rule A into policy X, while node 2 attempts to delete policy X, rule A may remain after policy X deletion.
For example, node 1 may execute this function [1] just after another node finishes executing this for-loop [2].
A proper fix may take some thought. May require the rules table to be locked while the delete_policy function is in progress.
[1] https:/
[2] https:/
| Changed in congress: | |
| milestone: | newton-rc1 → newton-rc2 |
Revision history for this message
| Eric K (ekcs) wrote | #1 |
| Changed in congress: | |
| milestone: | newton-rc2 → ocata-1 |
| Changed in congress: | |
| milestone: | ocata-1 → ocata-2 |
| Changed in congress: | |
| milestone: | ocata-2 → ocata-3 |
| assignee: | nobody → Eric K (ekcs) |
| Changed in congress: | |
| status: | New → Triaged |
| Changed in congress: | |
| milestone: | ocata-3 → none |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on congress (master) | #2 |
To post a comment you must log in.
Retargeting for ocata because this is a low encounter-