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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235169 Title: Fails to read files in /etc/network/interfaces.d/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1235169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
