[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-07-11 Thread Scott Moser
fix is now released to xenial under bug 1595302. daily cloud-images with this newer version of cloud-init should appear in the next few days. Any image with a serial number *newer* than 20160707 should have cloud-init at 0.7.7~bzr1246-0ubuntu1~16.04.1 . ** Changed in: cloud-init (Ubuntu Xenial)

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-06-23 Thread Scott Moser
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial)

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-06-04 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init - 0.7.7~bzr1227-0ubuntu1 --- cloud-init (0.7.7~bzr1227-0ubuntu1) yakkety; urgency=medium * New upstream snapshot. - fix one more unit test to run inside buildd. -- Scott Moser Sat, 04 Jun 2016 20:55:07 -0400

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-06-03 Thread Launchpad Bug Tracker
** Branch linked: lp:cloud-init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev rules To manage notifications about this bug go to:

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-06-01 Thread Scott Moser
** No longer affects: ifupdown (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev rules To manage notifications about this bug go to:

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-05-27 Thread Launchpad Bug Tracker
** Branch linked: lp:~smoser/cloud-init/trunk.fix-networking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev rules To manage notifications

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-05-09 Thread Scott Moser
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-05-09 Thread Scott Moser
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577844 Title: Drop unnecessary blocking of all net udev rules To manage

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-05-04 Thread Martin Pitt
Also note that blocking the uevents will not actually work for the renaming if there is an initramfs involved. I. e. it will work in containers, but not QEMU or bare metal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-05-04 Thread Scott Moser
some futher thought one reason for the blocking of udev was to have the .link files that cloud-init wrote apply. It turns out that systemd.link will only rename devices once (based on a property in the devices /sys that says it has been renamed). So, for cloud-init to have these apply we will

[Bug 1577844] Re: Drop unnecessary blocking of all net udev rules

2016-05-04 Thread Scott Moser
some futher thought one reason for the blocking of udev was to have the .link files that cloud-init wrote apply. It turns out that systemd.link will only rename devices once (based on a property in the devices /sys that says it has been renamed). So, for cloud-init to have these apply we will