kernel-packages team mailing list archive

[James Page <james.page@xxxxxxxxxx>]

** Changed in: linux (Ubuntu)
       Status: Confirmed => Won't Fix

-- 
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/1068365

Title:
  openvswitch gre tunnels not working in quantal

Status in “linux” package in Ubuntu:
  Won't Fix
Status in “openvswitch” package in Ubuntu:
  Fix Released
Status in “linux” source package in Quantal:
  Won't Fix
Status in “openvswitch” source package in Quantal:
  Fix Released
Status in “linux” source package in Raring:
  Won't Fix
Status in “openvswitch” source package in Raring:
  Fix Released

Bug description:
  [Impact]
  Quantal currently only has the openvswitch module provided via the kernel; this does not support gre tunnels between switches which is used extensively by OpenStack Quantum.  The DKMS module which is currently disabled in quantal provides these and other features.  This is a regression compared to precise which ships the dkms module.

  [Test Case]
  Serges charm is a excellent way to test this - see lp:~serge-hallyn/charms/quantal/ovs-lxc/trunk

  juju deploy local:ovs-lxc master
  juju deploy local:ovs-lxc slave
  juju add-relation master:master slave:slave
  juju ssh slave/0
  sudo lxc-start -n quantal-amd64-pristine

  LXC instances will not get an IP address from the DHCP server running
  on the master.

  sudo ovs-dpctl show -s
  Will not show a gre entry for the configured pipe (its non-functional)

  [Regression Potential]
  The fix pull in 8 cherry picked commits from upstream trunk which are predominately targetted at the datapath component (currently disabled) so are well contained.

  These picks fixup support for the 3.5 kernel and rename the the dkms
  provided modules to remove the _mod suffix (aligning to the kernel
  module naming).

  There are some changes in the ovs scripts which are used during init
  control of openvswitch.

  [Original Bug]
  I use the charm at lp:~serge-hallyn/charms/quantal/ovs-lxc to fire up a pair of lxc nodes.  The hooks/install file will show how the nodes are set up.  Each node has an openvswitch bridge with a gre tunnel with the other node as remote_ip, and a dnsmasq on the master lxc host.  It creates containers which have eth1 slaved to the openvswitch bridge.

  On precise (using lp:~serge-hallyn/charms/precise/ovs-lxc) this works.
  Containers on slave nodes get ip addresses from the dnsmasq on the
  master, and can communicate to each other over the private
  192.168.100.x subnet.  Precise is using the openvswitch_mod kernel
  module.

  On quantal, which uses the upstream openvswitch kernel module, it does
  not work.  When I create a container on the slave, and run dhclient on
  its 'eth1' which is slaved to the openvswitch bridge, tcpdump on the
  slave host shows the queries on ovbr0 (the openvswitch bridge) but not
  on eth0.

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