Ambiguous default direction for policy classifier
Bug #1516803 reported by
Sumit Naiksatam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy |
Fix Released
|
Medium
|
Sumit Naiksatam | ||
Group Based Policy Client |
In Progress
|
Medium
|
Sumit Naiksatam |
Bug Description
When no direction is specified while creating a policy classifier, the semantics of the enforced direction may vary depending on the backend implementation. Its not clear to the user as to what behavior he should expect.
We should decide what the default direction should be (most likely "bi") when no direction is explicitly specified and persist that in the backend. The user will then clearly see this direction and there will not be any ambiguity.
Changed in group-based-policy-client: | |
assignee: | nobody → Sumit Naiksatam (snaiksat) |
milestone: | none → 1.0.0 |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in group-based-policy: | |
status: | New → Confirmed |
Changed in group-based-policy-client: | |
status: | Confirmed → In Progress |
Changed in group-based-policy: | |
milestone: | next → liberty-1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
CLI fixed by: https:/ /review. openstack. org/#/c/ 246081