[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target
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) Status: New => Incomplete ** No longer affects: systemd (Ubuntu Xenial) ** No longer affects: systemd (Ubuntu Yakkety) -- 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 removed before firing units depending on network-online.target Status in systemd package in Ubuntu: Fix Released Bug description: [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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface 2. Create unit with After=network-online.target that pings a host over ipv6 3. Restart the system (may need several reboots as it's a race condition) [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target
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 removed before firing units depending on network-online.target Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Bug description: [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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface 2. Create unit with After=network-online.target that pings a host over ipv6 3. Restart the system (may need several reboots as it's a race condition) [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target
@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 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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface 2. Create unit with After=network-online.target that pings a host over ipv6 - 3. Restart the system + 3. Restart the system (may need several reboots as it's a race condition) [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition -- 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 removed before firing units depending on network-online.target Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Bug description: [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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface 2. Create unit with After=network-online.target that pings a host over ipv6 3. Restart the system (may need several reboots as it's a race condition) [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target
** 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 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 removed before firing units depending on network-online.target Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Bug description: [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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface 2. Create unit with After=network-online.target that pings a host over ipv6 3. Restart the system [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673092] Re: systemd doesn't wait until the tentative flag isn't removed before firing units depending on network-online.target
** 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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface - 2. Create unit with After=network-online.target and pings a host over -ipv6 + 2. Create unit with After=network-online.target that pings a host over + ipv6 3. Restart the system [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant - (upstream bug report uses networkd, while I use ifupdown) - + (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition -- 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 removed before firing units depending on network-online.target Status in systemd package in Ubuntu: New Bug description: [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 here [1], but ideally systemd should wait until the tentative flag is removed. v232 doesn't have this issue. Can the relevant patches be backported to LTS releases? [Test Case] 1. Configure ipv6 address on one interface 2. Create unit with After=network-online.target that pings a host over ipv6 3. Restart the system [Regression Potential] * Unknown [Other Info] * Seems to have been fixed on v232. * Using ifupdown or networkd to create the interface seems to be irrelevant (upstream bug report uses networkd, while I use ifupdown) [1]: https://www.agwa.name/blog/post/beware_the_ipv6_dad_race_condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
