Cisco CSR1kv device driver should set 'protocol' value to 'all' or to any valid protocol name.

Bug #1463777 reported by Nikolay Fedotov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-cisco
New
Undecided
Unassigned
neutron
Won't Fix
Undecided
Unassigned

Bug Description

If user set protocol to 'any' (using neutron client or horizon) the CSR1kv device driver sends following request:

{"rules": [{"L4-options": {"dest-port-start": "22"}, "protocol": "tcp", "sequence
": "100", "destination": "any", "source": "any", "action": "permit"}, {"action": "permit", "source": "any", "destination": "any", "protocol": null, "sequence": "101"}]}

Notice: "protocol": null,

'null' is not a valid value. According to Reference Guide: A protocol number or any of the keywords "all", "tcp", "udp", "icmp","ip"

Tags: fwaas
Yanping Qu (yanping)
Changed in neutron-fwaas (Ubuntu):
assignee: nobody → Yanping Qu (yanping)
Yanping Qu (yanping)
affects: neutron-fwaas (Ubuntu) → neutron
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Can you confirm that this is something that belongs to the neutron core, rather than the cisco driver?

Changed in neutron:
status: New → Incomplete
Revision history for this message
Yanping Qu (yanping) wrote :

This is an issue specific to Cisco FWaaS driver.

Revision history for this message
Akihiro Motoki (amotoki) wrote :

Vendor FWaaS drivers are in-tree of neutron-fwaas, so I think it is valid.

Changed in neutron:
status: Incomplete → Confirmed
Changed in neutron:
assignee: Yanping Qu (yanping) → Abhishek Tiwary (abhishek-tiwary2)
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 172 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Abhishek Tiwary (abhishek-tiwary2) → nobody
status: Confirmed → Incomplete
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

tags: added: fwaas
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Bug closed due to lack of activity, please feel free to reopen if needed.

Changed in neutron:
status: Incomplete → Won't Fix
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.