This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1504154

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Tags added: trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1504154

Title:
  OVS with GRE tunnels no longer works

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have OpenStack environment with OVS with GRE tunnels between Compute
  nodes.

  All nodes OpenStack nodes have:
  Description:  Ubuntu 14.04.2 LTS
  Release:      14.04

  After upgrading kernel from 3.13.0-45 to 3.13.0-46 on one Compute node 
OpenStack networking on this node no longer works.
  It also does not work on any newer version up to 3.13.0-65.

  Everything looks OK, bridges and ports are configured in OVS, but
  there is no communication - VMs can't receive network configuration
  from DHCP agent running on another server.

  The same is with 3.16 kernel:

  Last working version is 3.16.0-30.
  With version 3.16.0-31and newer up to 3.16.0-50 network communication does 
not work.

  I analyzed changes included in 3.13.0-46 and 3.16.0-31 and both have the same 
change regarding GRE:
  * gre: fix the inner mac header in nbma tunnel xmit path

  Maybe this is the reason?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504154/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to