yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49040
[Bug 1495960] Re: linuxbridge with vlan crashes when long device names used
Reviewed: https://review.openstack.org/246954
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ececa3a20e19985b7ebcca2c629126a3900c090
Submitter: Jenkins
Branch: master
commit 7ececa3a20e19985b7ebcca2c629126a3900c090
Author: Andreas Scheuring <andreas.scheuring@xxxxxxxxxx>
Date: Wed Nov 18 15:33:03 2015 +0100
lb: interface name hashing for too long vlan interface names
The linuxbridge agent creates vlan subinterfaces for each vlan
neutron network. The name for this vlan subinterface is
"<phys-interface>.<vlan-id>". Todays code crashes if the
physical interface name is too long. Therefore this hashing is
being introduced.
Change-Id: Ieb3c0a7282b28eed556236ead4993ab83a29a12f
Closes-Bug: #1495960
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1495960
Title:
linuxbridge with vlan crashes when long device names used
Status in neutron:
Fix Released
Bug description:
The linuxbridge agent creates a linux vlan-device for each openstack vlan network that has been defined. Therefore the code uses the following naming scheme : <eth-dev-name>.<vlan-id>
Example: eth-dev-name: eth0, vlan-id: 1000 --> eth0.1000
This works fine, if eth-dev-name is a short name like "eth0". If there
is a long device name (e.g. long-device-name) this will cause trouble,
as the vlan device name "long-device-name.1000" exceeds the max length
of a linux network device, which is 15 chars.
Today the linuxbridge agent fails with
Command: ['ip', 'link', 'add', 'link', 'too_long_name', 'name', 'too_long_name.1007', 'type', 'vlan', 'id', 1007]
Exit code: 255
Stderr: Error: argument "too_long_name.1007" is wrong: "name" too long
The same problem needs to be solved for the new macvtap agent that is
currently under development [1] as well
[1] https://bugs.launchpad.net/neutron/+bug/1480979
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1495960/+subscriptions
References