[Bug 1565804] Re: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists
Andrew McDermott
andrew.mcdermott at canonical.com
Mon Apr 4 14:20:58 UTC 2016
The Juju bridge script, when creating the bridge device, generally
leaves all iface options as it found them.
For example:
auto eth1.16
iface eth1.16 inet static
address 10.245.184.100/24
vlan-raw-device eth1
mtu 1500
vlan_id 16
becomes the following:
iface eth1.16 inet manual
address 10.245.184.100/24
vlan-raw-device eth1
mtu 1500
vlan_id 16
auto br-eth1.16
iface br-eth1.16 inet static
address 10.245.184.100/24
mtu 1500
bridge_ports eth1.16
bridge_stp off
bridge_maxwait 0
Note: It doesn't propagate any bond options.
For example:
auto eth0
iface eth0 inet manual
bond-lacp_rate slow
bond-xmit_hash_policy layer2
bond-miimon 100
bond-master bond0
mtu 1500
bond-mode active-backup
[ skipping eth1 for clarity ]
auto bond0
iface bond0 inet dhcp
bond-lacp_rate slow
bond-xmit_hash_policy layer2
bond-miimon 100
mtu 1500
bond-mode active-backup
hwaddress 52:54:00:1c:f1:5b
bond-slaves none
becomes the following when bridged:
auto eth0
iface eth0 inet manual
bond-lacp_rate slow
bond-xmit_hash_policy layer2
bond-miimon 100
bond-master bond0
mtu 1500
bond-mode active-backup
auto bond0
iface bond0 inet manual
bond-lacp_rate slow
bond-xmit_hash_policy layer2
bond-miimon 100
mtu 1500
bond-mode active-backup
hwaddress 52:54:00:1c:f1:5b
bond-slaves none
dns-nameservers 10.17.20.200
dns-search maas19
auto br-bond0
iface br-bond0 inet dhcp
mtu 1500
hwaddress 52:54:00:1c:f1:5b
bridge_ports bond0
bridge_stp off
bridge_maxwait 0
dns-nameservers 10.17.20.200
dns-search maas19
I generally propagated the existing options when creating the bridge
device. Should MTU be an exception now?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1565804
Title:
ifup of vlan interfaces failing during networking start - RTNETLINK
answers: File exists
Status in ifupdown package in Ubuntu:
New
Bug description:
/e/n/i:
auto lo
iface lo inet loopback
dns-nameservers 10.245.168.2
dns-search dellstack
auto eth0
iface eth0 inet static
gateway 10.245.168.1
address 10.245.168.17/21
dns-nameservers 10.245.168.2
mtu 1500
auto eth1
iface eth1 inet manual
mtu 1500
auto eth1.2667
iface eth1.2667 inet static
address 10.245.184.20/24
vlan-raw-device eth1
mtu 9000
vlan_id 2667
output from networking startup:
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Mon 2016-04-04 12:14:26 UTC; 1h 33min ago
Docs: man:interfaces(5)
Process: 1255 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 868 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited,
Main PID: 1255 (code=exited, status=1/FAILURE)
Apr 04 12:14:25 reflecting-attraction systemd[1]: Starting Raise network interfaces...
Apr 04 12:14:26 reflecting-attraction ifup[1255]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Apr 04 12:14:26 reflecting-attraction ifup[1255]: RTNETLINK answers: File exists
Apr 04 12:14:26 reflecting-attraction ifup[1255]: Failed to bring up eth1.2667.
Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 12:14:26 reflecting-attraction systemd[1]: Failed to start Raise network interfaces.
Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Unit entered failed state.
Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Failed with result 'exit-code'.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ifupdown 0.8.10ubuntu1
ProcVersionSignature: User Name 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Mon Apr 4 13:42:48 2016
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1565804/+subscriptions
More information about the foundations-bugs
mailing list