Since end of 2014 IPv6 traffic causes host to reboot

Bug #1460105 reported by Imad Benbrahim
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

Bug Description

We launch IPv6 traffic to a VM within an Openstack Host that has icehouse. Soon the host restarts. In /var/log/messages and /var/log/openvswitch/ovs-vswitchd.log we see multiple instances of this error:
      ovs-vswitchd: ovs|00025|odp_util(revalidator_20)|ERR|mask expected for non-Ethernet II frame

We tried the same test on multiple other machines that have slightly different versions of neutron. Our conclusion is that the bug must have been introduced with :
    openstack-neutron.noarch 2014.1.3-5.el6
    openstack-neutron-ml2.noarch 2014.1.3-5.el6
    openstack-neutron-openvswitch.noarch 2014.1.3-5.el6
    python-neutron.noarch 2014.1.3-5.el6

Machines with the above version (or later) will exhibit the bug.

Machines with the following version will work fine:
    openstack-neutron.noarch 2014.1.3-4.el6
    openstack-neutron-ml2.noarch 2014.1.3-4.el6
    openstack-neutron-openvswitch.noarch 2014.1.3-4.el6
    python-neutron.noarch 2014.1.3-4.el6

Tags: ipv6
Revision history for this message
Imad Benbrahim (ibenbrahim) wrote :
affects: openstack-community → neutron
Revision history for this message
Sean M. Collins (scollins) wrote :

What version of Open vSwitch are you running? I haven't looked at your logs to see if it prints the version, but if the host is rebooting- that is most likely due to a kernel panic

tags: added: ipv6
Revision history for this message
Imad Benbrahim (ibenbrahim) wrote :

openvswitch version is identical on both machines: 2.1.2-1.el6.
The theory about neutron version 2014.1.3-4 working better may not hold according the latest tests. The problem seems to happen randomly in some machines that have icehouse on top of CentOS 6.5.

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:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
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.