ICMP security group rules should have a type and code params instead of using "--port-range-min" and "--port-range-max"
Bug #1251224 reported by
Rami Vaknin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Undecided
|
Unassigned |
Bug Description
Version
======
Havana on rhel
Description
=========
I couldn't find a doc specifying whether icmp security group rules ignore the "--port-range-min" and "--port-range-max" params or use then as code and type as we know from nova security group rules.
I think that it should be:
i. Well documented.
ii. prohibited for use of "--port-range-min" and "--port-range-max" in icmp rules context, new switches should be created for code and type.
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
assignee: | nobody → Edgar Magana (emagana) |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: doc |
tags: | removed: l3-ipam-dhcp |
To post a comment you must log in.
I would expect the following doc to be updated: docs.openstack. org/network- admin/admin/ content/ securitygroup_ api_abstraction s.html
http://