yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #42867
[Bug 1326907] Re: neutron-openvswitch-agent on fedora 20: SystemError: Unable to determine kernel version for Open vSwitch with VXLAN support.
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1326907
Title:
neutron-openvswitch-agent on fedora 20: SystemError: Unable to
determine kernel version for Open vSwitch with VXLAN support.
Status in neutron:
Expired
Bug description:
On Fedora 20, neutron-openvswitch-agent fails to start with the
following error:
2014-06-05 16:15:55.379 5266 TRACE
neutron.plugins.openvswitch.agent.ovs_neutron_agent SystemError:
Unable to determine kernel version for Open vSwitch with VXLAN
support. To use VXLAN tunnels with OVS, please ensure that the version
is 1.10 or newer!
In neutron/agent/linux/ovs_lib.py, the code is attempting to determine
the installed version of the openvswitch module by calling:
modinfo openvswitch
It's looking for a line containing "version: ", but "modinfo" produces
no such line; the output looks like this:
filename: /lib/modules/3.11.10-301.fc20.x86_64/kernel/net/openvswitch/openvswitch.ko
license: GPL
description: Open vSwitch switching datapath
depends: gre
intree: Y
vermagic: 3.11.10-301.fc20.x86_64 SMP mod_unload
signer: Fedora kernel signing key
sig_key: 03:59:1D:C5:7A:69:07:41:40:1A:1C:20:2E:2B:3D:9F:4F:ED:2A:0E
sig_hashalgo: sha256
We can fix this by also looking at the "vermagic: " line, but I
question whether this test should even be here. The output of
"modinfo" wasn't designed to be machine parse-able, and it is
demonstrably not stable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1326907/+subscriptions
References