[Bug 1235169] Re: Fails to read files in /etc/network/interfaces.d/

[Tom Reynolds]

I just spent 3 days trying to understand why the one and only network
interface on a remote server where my only out of band access mechanism
is a netboot recovery system would not come up, and not log any error.
Whoever introduced this new mechanism should maybe have tested it.

Said system runs saucy amd64 with the saucy-updates repository and all
available updates installed. ifupdown is at 0.7.44ubuntu3, i.e. this bug
is unfixed for me as of today. I've worked around it by moving
/etc/network/interfaces out of the way, placing the network
configuration in a new /etc/network/interfaces file.

-- 
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/1235169

Title:
  Fails to read files in /etc/network/interfaces.d/

Status in “ifupdown” package in Ubuntu:
  Fix Released

Bug description:
  0.7.44ubuntu3 on Saucy 13.10 amd64.

  On a multi-homed server with five ethernet interfaces we have 6
  'interfaces' files in '/etc/network/interfaces.d/' for 'lo' and 'eth0'
  through 'eth4'.

  ifup -a fails to include the contents of these files and consequently
  the interfaces are ignored.

  "strace" reveals that when scanning the 'interfaces.d' directory
  ifupdown is using the "openat()" function which does an integral
  change-directory. It gets the list of files correctly and "closes()"
  the directory. It then does "open()" on each validly named file but
  gets  -ENOENT result because it forgets to prefix the file-name with
  the 'interfaces.d/' directory - so it is looking in the current
  working directory rather than '/etc/network/interfaces.d/'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1235169/+subscriptions