"ANY" protocol option to create GBP Class should be removed from UI
Bug #1416471 reported by
puppet-py
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy UI |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In UI(Horizon)creating a GBP Class with protocol option "ANY" will fail.
We should :
1. Either remove the ANY option
2. OR, implicitly allow ALL Protocols under the ANY option
affects: | group-based-policy-client → group-based-policy-ui |
Changed in group-based-policy-ui: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → kilo-gbp-4 |
Changed in group-based-policy-ui: | |
milestone: | kilo-gbp-4 → next |
Changed in group-based-policy-ui: | |
milestone: | next → liberty-1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
In the same form referred by this bug, the UI is showing many other unsupported protocols (HTTPS / DNS etc...).
As far as the API is concerned, only protocol values [None, 'tcp', 'udp', 'icmp'] and their integer representation (0 to 255) are supported.