IPv6 Scenario tests should use icmpv6 protocol for Security Group rule

Bug #1671366 reported by Sridhar Gaddam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Won't Fix
Undecided
Sridhar Gaddam

Bug Description

Currently to validate some IPv6 scenario tests, tempest uses ping6 to check the IPv6 connectivity between VMs spawned on a network.
Before validating ping6, tempest configures a Security Group rule with ethertype='IPv6' and protocol='icmp'.

While this is not a problem with the reference firewall driver in Neutron, in OpenDaylight we noticed that SG rule was configured with icmp as per the rule and IPv6 Scenario tests are failing.

Ideally, tempest should configure ICMPv6 rule with protocol='icmpv6' and not with protocol='icmp'

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/443444

Changed in tempest:
assignee: nobody → Sridhar Gaddam (sridhargaddam)
status: New → In Progress
Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

yea icmpv6 seems right way to pass as protocol for ipv6 sec grp to avoid duplicate entry in neutron but can you please give more information on failure with 'icmp' ?

neutron should support legacy 'icmp' also.

Revision history for this message
Sridhar Gaddam (sridhargaddam) wrote :

Agree that Neutron should support icmp for backward compatibility. Here, I'm taking about an issue that is observed when using Neutron+OpenDaylight and not with Neutron ML2/OVS reference implementation.

API tests in Neutron would validate that icmp can be supplied for backward compatibility.
But tempest IPv6 "Scenario tests" should ideally use "icmpv6" and not icmp.

Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

Sure, let's find the best way to go on this. started mail thread- http://lists.openstack.org/pipermail/openstack-dev/2017-March/114570.html

Revision history for this message
Sridhar Gaddam (sridhargaddam) wrote :

Thanks @Ghanshyam, I've replied to the thread.

Also, I would like to clarify that tempest should validate Neutron API is supporting the different configuration methods like icmp/icmpv6/ipv6-icmp etc for backward compatibility. But, such tests should be part of API tests and not the scenario tests. IMO, the tempest scenario test should use the right value (i.e., protocol=icmpv6).

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tempest (master)

Change abandoned by Sridhar Gaddam (<email address hidden>) on branch: master
Review: https://review.openstack.org/443444

Revision history for this message
Ken'ichi Ohmichi (oomichi) wrote :

The comment from the corresponding patch:

"Ideally neutron should support all of them. Anyways, as discussed in the email thread [*], the real fix should be in Neutron. So, abandoning this patch."

[*] http://lists.openstack.org/pipermail/openstack-dev/2017-March/114614.html

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