openvswitch gre tunnels not working in quantal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Critical
|
Unassigned | ||
Quantal |
Won't Fix
|
Critical
|
Unassigned | ||
Raring |
Won't Fix
|
Critical
|
Unassigned | ||
openvswitch (Ubuntu) |
Fix Released
|
Critical
|
James Page | ||
Quantal |
Fix Released
|
Critical
|
James Page | ||
Raring |
Fix Released
|
Critical
|
James Page |
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-
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.
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Quantal): | |
status: | Confirmed → Won't Fix |
Changed in linux (Ubuntu Raring): | |
status: | Confirmed → Won't Fix |
Changed in linux (Ubuntu): | |
status: | Confirmed → Won't Fix |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1068365
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.