protocol-range in policy-classifier cannot be unset

Bug #1407324 reported by puppet-py
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy
Confirmed
Medium
Sumit Naiksatam

Bug Description

In policy-classifier , port-range attribute once set by user using CLI/GUI cannot be unset/updated to default/none.

test@localhost:~/devstack$ gbp policy-classifier-create test --port-range 300:500
Created a new policy_classifier:
+-------------+--------------------------------------+
| Field | Value |
+-------------+--------------------------------------+
| description | |
| direction | |
| id | 3ed590f7-51fe-47ff-8cbc-18f4a74f060b |
| name | test |
| port_range | 300:500 |
| protocol | |
| shared | False |
| tenant_id | 3b4eb7e4327b4d90be39288b2e8dd163 |
+-------------+--------------------------------------+
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-classifier-update test --port-range ''
Bad Request (HTTP 400) (Request-ID: req-8ffc4baa-443b-4613-96b6-a677b4669375)
test@localhost:~/devstack$
test@localhost:~/devstack$
test@localhost:~/devstack$ gbp policy-classifier-update test --port-range None
Bad Request (HTTP 400) (Request-ID: req-381878f1-8066-459a-8a83-f8f3c4062228)
test@localhost:~/devstack$

affects: group-based-policy-client → group-based-policy
Changed in group-based-policy:
milestone: none → kilo-gbp-1
assignee: nobody → Sumit Naiksatam (snaiksat)
importance: Undecided → Medium
status: New → Confirmed
tags: added: juno-backport-potential
Changed in group-based-policy:
milestone: kilo-gbp-1 → kilo-gbp-2
Changed in group-based-policy:
milestone: kilo-gbp-2 → kilo-gbp-3
Changed in group-based-policy:
milestone: kilo-gbp-3 → next
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.