[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-10-11 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: nplan (Ubuntu) Status: New => Triaged ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Xenial) Importance: Undecided Status: New

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-10-04 Thread Ryan Harper
I re-ran the recreate on a daily artful image, updated cloud-init in the image to use the udevadm trigger as before and noticed that it still fails to apply the MTU to the second interface. Taking the suggestion of including a udevadm control reload, I further modified the image to add that reload

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-10-04 Thread Dimitri John Ledkov
@original reporter have you added `udevadm control --reload` in the appropriate points in the test-harness and/or cloud-init? And does this resolve the race you have previously observed? Unassigning, Removing artful series target and marking incomplete, until further information is provided. ** N

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-09-29 Thread Francis Ginther
** Tags added: id-597a09900a9f730ee1bfade0 -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules becau

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-09-19 Thread Dimitri John Ledkov
Something similar got reported recently upstream, and I got a brand new discovery that one should actually call $ udevadm control --reload -> whenever configuration is changed, as upstream knows that all of their internal state caching and reloading is racy. Could you please modify your reproducer

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-09-11 Thread Patricia Gaughen
** Changed in: systemd (Ubuntu Artful) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1669564 Title: udevadm trigger

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-08-09 Thread Ryan Harper
Revisting this on an artful image, and nothing besides the driver replug (what netplan apply does) appears to work to process .link files. Something changed I suspect in systemd w.r.t the builtin-test setup_net_link path which would process .link files. -- You received this bug notification beca

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-07-27 Thread Steve Langasek
** Summary changed: - udevadm trigger subsystem-match=net doesn't always run rules + udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Also affects: systemd (Ubuntu Artful)