[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target

2017-06-20 Thread Dimitri John Ledkov
This is incomplete request, essentially requesting "backport all of networkd" which is not appropriate for a targetted fixes that SRUs require. Can you not use zesty on your system? ** Changed in: systemd (Ubuntu Xenial) Status: New => Incomplete ** Changed in: systemd (Ubuntu Yakkety)

[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target

2017-04-03 Thread Dimitri John Ledkov
zesty ships v232 hence marked as fix released for zesty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1673092 Title: systemd doesn't wait until the tentative flag isn't

[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target

2017-04-01 Thread Braiam Peguero
@xnox There isn't anything indicating in the changelogs that this bug was fixed and 229-4ubuntu17. Remember that the bug is a race condition, so it may or may not happen at random, it depends which is faster, systemd or DAD ** Description changed: [Impact] See this issue for details http

[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target

2017-03-28 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a m

[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target

2017-03-15 Thread Braiam Peguero
** Description changed: [Impact] See this issue for details https://github.com/systemd/systemd/issues/2037 Basically, while DAD is running checks on a ipv6 address, no service can bind the interface, which could provoke units to fail. Disabling DAD is a workaround as explained he