[Bug 1565804] Re: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists

[Kees Hoekzema]

I had/have sort of the same problem, when running the network startup it
somehow wants to set up my vlans twice; i think when i do the 'master'
interface, and once when it sets up the normal interface.

The first time it just sets up the vlan and assigns an address. The
second time it tries to add that address again, but that obviously fails
with an 'RTNETLINK answers: File exists'

And because the default (since 2014?) is to treat any error as fatal it
just stops configuring the interface even tho it would be perfectly ok
to at least try to set, for example, the default route or the 'up'
statements. But no, a small step failed so it's better to leave the
interface half configured.

On Ubuntu 16.04 this can be worked around by adding
"EXCLUDE_INTERFACES=' --ignore-errors' " to /etc/default/networking so
ifupdown does the sensible thing and tries to continue after an error
instead of leaving a half configured interface.

-- 
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:
  Confirmed

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