"--protocol None" is rejected in security-group-rule-create
Bug #1469642 reported by
Masaki Matsushita
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Expired
|
Undecided
|
Unassigned |
Bug Description
When invalid protocol specified in security-
% neutron security-
Security group rule protocol foo not supported. Only protocol values [None, 'tcp', 'udp', 'icmp', 'icmpv6'] and integer representations [0 to 255] are supported.
However, neutron-server rejects "None" for protocol.
% neutron security-
Security group rule protocol None not supported. Only protocol values [None, 'tcp', 'udp', 'icmp', 'icmpv6'] and integer representations [0 to 255] are supported.
I think this behavior is confusing.
Changed in python-neutronclient: | |
assignee: | nobody → Masaki Matsushita (mmasaki) |
status: | New → In Progress |
Changed in python-neutronclient: | |
assignee: | nobody → li,chen (chen-li) |
status: | Incomplete → In Progress |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 196582/