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

This bug was fixed in the package nplan - 0.32~17.04.1 --- nplan (0.32~17.04.1) zesty; urgency=medium * Backport 0.32 to 17.04. (LP: #1713142) nplan (0.32) bionic; urgency=medium * src/nm.c: better handle the UUID generation; the order of iterating through interaces may

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

This bug was fixed in the package nplan - 0.32~16.04.3 --- nplan (0.32~16.04.3) xenial; urgency=medium * tests/integration.py: Really fix skipping test_routes_v6 for the NM backend. nplan (0.32~16.04.2) xenial; urgency=medium * tests/integration.py: Fix test_routes_v6 that

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

This bug was fixed in the package nplan - 0.32~17.10.1 --- nplan (0.32~17.10.1) artful; urgency=medium * Backport 0.32 to Ubuntu 17.10. (LP: #1713142) nplan (0.32) bionic; urgency=medium * src/nm.c: better handle the UUID generation; the order of iterating through interaces

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

verification-done for artful with 0.32~17.10.1: As above, MTU changes are applied correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net

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

verification-done for xenial 0.32~16.04.3, and zesty 0.32~17.04.1: netplan appears to behave correctly w.r.t setting MTU, using the example from Ryan the MTU appears to be correctly applied every time. ** Tags removed: verification-needed verification-needed-artful verification-needed-xenial

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

Hello Ryan, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

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

Hello Ryan, or anyone else affected, Accepted nplan into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

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

Autopktests still failing for xenial; the test is still not being skipped (we know it won't work on Xenial due to the version of NM shipped there). Marking verification-failed-xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug

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

Hello Ryan, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

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

nplan 0.32~16.04.2 fails to build because I mismerged 0.32 and broke the code skipping the test_routes_v6 test in the NetworkManager case. Therefore, it can't possibly pass SRU verification. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received

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

I cannot verify this one yet, the previous SRU to xenial has blocked this: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1713142 On Thu, Nov 23, 2017 at 11:00 AM, Łukasz Zemczak <1669...@bugs.launchpad.net > wrote: > Hello Ryan, or anyone else affected, > > Accepted nplan into

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

Hello Ryan, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

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

Hello Ryan, or anyone else affected, Accepted nplan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

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

** Description changed: + [Impact] + Proper udev trigger behavior following a 'netplan apply' is essential to having all the configuration applied for an interface. + + [Test case] + 1- Write a netplan configuration file that sets MTU for a device, or renames a device. + 2- Run 'netplan apply'

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

Can we get the description follow https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ? Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger

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

This bug was fixed in the package nplan - 0.32 --- nplan (0.32) bionic; urgency=medium * src/nm.c: better handle the UUID generation; the order of iterating through interaces may affect things here. Also make sure the tests catch a null UUID. -- Mathieu Trudel-Lapierre

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

On Wed, Nov 1, 2017 at 8:11 AM, Dimitri John Ledkov wrote: > I have merged the netplan code to that effect in netplan master now - > i.e. generate reloads udevadm rules. > > However, I have now realised something. > > MTUBytes can be set in two places: NetDev.MTUBytes key

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

I have merged the netplan code to that effect in netplan master now - i.e. generate reloads udevadm rules. However, I have now realised something. MTUBytes can be set in two places: NetDev.MTUBytes key in the .link file and in Link.MTUBytes key in the .network file. The .link setting is applied

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

I agree, made a merge proposal to the same effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of

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

** Merge proposal linked: https://code.launchpad.net/~xnox/netplan/+git/netplan/+merge/332151 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net

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

** 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:

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

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

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

@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. **

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

** Tags added: id-597a09900a9f730ee1bfade0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration

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

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

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

** Changed in: systemd (Ubuntu Artful) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net

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

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

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

** 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)