[Touch-packages] [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:

[Touch-packages] [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

[Touch-packages] [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. **

[Touch-packages] [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 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

[Touch-packages] [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

[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm

[Touch-packages] [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

[Touch-packages] [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)

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

On Tue, May 2, 2017 at 8:54 AM, Dimitri John Ledkov wrote: > Ideally, the following should happen: > * boot > * Created link configuration context > > * Check if link configuration needs reloading -> appears in the debug logs > * New MTU is successfully applied > Let me

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

Ideally, the following should happen: * boot * Created link configuration context * Check if link configuration needs reloading -> appears in the debug logs * New MTU is successfully applied If the 'Check ...' is missing from the debug logs, after netplan has run, udevd will not reload the

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

Hm. udevd applies MTU property from the link file in the link_config_apply() function, which is called by builtin_net_setup_link(), from the net_setup_link builtin. Reading the conditions for builtin_net_setup_link_init() and builtin_set_setup_link_validate(), the link configuration context is

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

On Tue, May 2, 2017 at 3:05 AM, Dimitri John Ledkov wrote: > Looking at the journal files from the netplan-udev that fail, I see that > links are already renamed, before cloud-init renders things: > > Mar 09 17:51:12 ubuntu kernel: virtio_net virtio0 ens3: renamed from

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

Looking at the journal files from the netplan-udev that fail, I see that links are already renamed, before cloud-init renders things: Mar 09 17:51:12 ubuntu kernel: virtio_net virtio0 ens3: renamed from eth0 Mar 09 17:51:12 ubuntu kernel: virtio_net virtio1 ens4: renamed from eth1 Mar 09 17:51:14

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

** Tags removed: rls-z-incoming ** Tags added: rls-aa-incoming -- 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

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

Script which launches the image created with the previous script to recreate issue. ** Attachment added: "02-netplan-udev-launch.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+attachment/4834862/+files/02-netplan-udev-launch.sh -- You received this bug notification

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

I've attached the requested journal. I've also attached two scripts which can be used to recreate the issue for further investigation. ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded

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

Here's the journal from a boot which fails. ** Attachment added: "netplan-udev-fail-journal.tgz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+attachment/4834860/+files/netplan-udev-fail-journal.tgz -- You received this bug notification because you are a member of Ubuntu

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

Script to generate a zesty cloud-image that can recreate the issue. ** Attachment added: "01-netplan-udev-recreate.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+attachment/4834861/+files/01-netplan-udev-recreate.sh -- You received this bug notification because you are

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

On Wed, Mar 8, 2017 at 5:03 AM, Dimitri John Ledkov wrote: > I wonder if following should be done (in netplan code that does the re- > trigger, or outside after .link files modified): > > $ sync > $ udevadm control --reload > $ udevadm trigger --verbose

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

I wonder if following should be done (in netplan code that does the re- trigger, or outside after .link files modified): $ sync $ udevadm control --reload $ udevadm trigger --verbose --subsystem-match=net --action=add This is a hypothesis, to try out first to reproduce the original bug, and then

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

We'd kind of need this to work anyway outside of the context of cloud- init-local. If one sets up netplan rules for a device, and for instance, attempts to set the MTU in networkd .link files, this change would not take effect until the system is rebooted. netplan could trigger --subsystem-

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

On Tue, Mar 7, 2017 at 9:41 AM, Dimitri John Ledkov wrote: > On 7 March 2017 at 14:37, Ryan Harper <1669...@bugs.launchpad.net> wrote: > > On Tue, Mar 7, 2017 at 6:27 AM, Dimitri John Ledkov < > launch...@surgut.co.uk> > > wrote: > > > >> Should one not restart

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

On 7 March 2017 at 14:37, Ryan Harper <1669...@bugs.launchpad.net> wrote: > On Tue, Mar 7, 2017 at 6:27 AM, Dimitri John Ledkov > wrote: > >> Should one not restart systemd-networkd after writing out .link et.al. >> units? >> > > systemd-networkd only deals with .netdev

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

On Tue, Mar 7, 2017 at 6:27 AM, Dimitri John Ledkov wrote: > Should one not restart systemd-networkd after writing out .link et.al. > units? > systemd-networkd only deals with .netdev and .network files; .link files are handled by udev This occurs during boot, before

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

Please provide full journal log for the boot. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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

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

Should one not restart systemd-networkd after writing out .link et.al. units? -- 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

** Tags added: rls-z-incoming -- 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 Status in

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

** Description changed: - root@ubuntu:~# lsb_release -rd + 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 - root@ubuntu:~# apt-cache policy udev + + 2. root@ubuntu:~# apt-cache policy udev udev: - Installed: 232-18ubuntu1 -