After picking apart; this is a known issue and does not break anything.
** Changed in: ifupdown (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524452
Title:
So unless ifup/ifdown brings the aliases up/down itself, I don't think
filtering those out is the right fix.
Take this scenario as an example:
- System boots quickly
- networking.conf kicks in, fails to bring eth0 because it's not showed up yet
(happen reasonably often with complex blade
It's definitely not the fix we want. Here's what's happening (after discussing
with smoser).
Each of the physical devices are brough up via ifup, and all semephor on
/run/networking/ looking for ifup.eth0, ifup.eth1 and ifup.eth1:1.
The first two files are written when
Possibly related to ifupdown since:
$ dpkg -S /etc/network/if-up.d/upstart
ifupdown: /etc/network/if-up.d/upstart
** Project changed: curtin => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If anyone wants to reproduce:
1. uvt-simplestreams-libvirt sync release=trusty arch=amd64
2. uvt-kvm create --memory 1024 --cpu 2 --disk 10 t1 release=trusty
3. uvt-kvm wait --insecure t1
4. uvt-kvm ssh --insecure t1
# inside t1 vm
5. edit /etc/network/interfaces to look like:
auto eth0
iface
