ICMP security group rule test the type or code should not None

Bug #1490281 reported by Dongcan Ye
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Invalid
Low
Unassigned

Bug Description

In security group rule with ICMP type and code test, it uses a pair (11, None) which expected to be handled as a wild-card within the type 11 (Time Exceeded).[1]

In Neutron API, it will checks params like type + code(None) or type(None) + code .
For example (None, 0) or (3, None). In this situation, Neutron should raise an exception.
Neutron bugs are here:
https://bugs.launchpad.net/neutron/+bug/1480966
https://bugs.launchpad.net/neutron/+bug/1489857

[1]https://github.com/openstack/tempest/blob/master/tempest/api/network/test_security_groups.py#L176

Dongcan Ye (hellochosen)
Changed in tempest:
assignee: nobody → Dongcan Ye (hellochosen)
Changed in tempest:
status: New → In Progress
Changed in tempest:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tempest (master)

Change abandoned by Dongcan Ye (<email address hidden>) on branch: master
Review: https://review.openstack.org/218660

Dongcan Ye (hellochosen)
Changed in tempest:
assignee: Dongcan Ye (hellochosen) → nobody
Revision history for this message
Rodrigo Duarte (rodrigodsousa) wrote :

According to afazekas comment at https://review.openstack.org/#/c/218250, this bug seems invalid.

Please reopen it with a more detailed description if you believe this is a real bug.

Changed in tempest:
status: In Progress → Invalid
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.