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

[Launchpad Bug Tracker]

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 affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is otherwise not
configured; this follows the same logic as setting IPv6AcceptRA=no in
networkd, with the exception that NM does not currently disable RAs. When
it does, an unconfigured device for IPv6 will truly be left with no config.

nplan (0.24) artful; urgency=medium

  * debian/control: set Priority to important to make sure we can get into
minimal.

 -- Mathieu Trudel-Lapierre   Thu, 16 Nov 2017
10:43:28 -0500

-- 
You received this bug notification because you are a 

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

[Launchpad Bug Tracker]

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 I clobbered when I re-applied
the skip rules for 16.04 after merging in 0.32.

nplan (0.32~16.04.1) xenial; urgency=medium

  * Backport netplan 0.32 to 16.04. (LP: #1713142)
  * debian/control: Depend on systemd (>= 229-4ubuntu20) for the PrimarySlave
feature backported in that revision.
  * tests/integration.py: Skip tests that are still not yet supported in xenial

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.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

nplan (0.30) artful; urgency=medium

  * Add an "optional" syntax node for now to all devices. This is unimplemented
for now, but intended to allow users to mark some devices as optional: to
make sure they do not delay boot when configured. (LP: #1664844)

nplan (0.29) artful; urgency=medium

  * Fix autopkgtests in a world where /run/NetworkManager/conf.d already
exists. nplan is enabled by default, so it might well have the directory
already created on the filesystem.

nplan (0.28) artful; urgency=medium

  * Revert 56cd3eec which disabled IPv6 Router Advertisements by default. It
broke default network config in LXD and was contrary to the defaults used
by the kernel. Reopens LP: 1655440. (LP: #1717404)
  * Add "accept-ra:" key for all device types; this will default to OFF but
allow users to disable processing Router Advertisements when required by
their network setup. (LP: #1655440)

nplan (0.27) artful; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix crash in systemd generator if called by an user on the command-line
  * coverage: fix exclusions to properly not cover our "never reached defaults"

  [ Dimitri John Ledkov ]
  * tests/integration.py: In teardown, stop systemd-networkd.socket.
  * src/networkd.c: Set UseMTU=true by default, whenever DHCP is in use.
(LP: #1717471)
  * tests/integration.py: fix resolved detection.

nplan (0.26) artful; urgency=medium

  * Bonding:
- Add support for specifying a primary slave. (LP: #1709135)
  * Rebind:
- Fix brcmfmac harder. Treat any 'brcmfmac' driver as not supporting
  rebind. (LP: #1712224)
  * Autopkgtests:
- Add allow-stderr. Systemd now bleats about a the networkd socket still
  being around and enabled when we restart the service; but we don't need
  to care since we're /restarting/ the service to load the new config.
- Fix the autostart package to be more sensible: we don't really care if
  networkd autostarts or not, but we need to make sure that our generator
  will run at boot, so instead check the state, but only assert it once
  we've added a config file and before checking the state of our dummy
  device.
- Do a bit more to make sure "mix" tests which stack virtual devices are
  as reliable as possible; by setting saner defaults.

nplan (0.25) artful; urgency=medium

  * tests/generate.py: add a test to validate that correct blacklist entries
are added when creating virtual devices.
  * tests/integration.py: clean up after br0 in networkd's test_bridge_mac; as
the remaining interface and udev configuration can confuse NetworkManager
now that it seems to manage random devices it did not create again.
(LP: #1699371)
  * src/nm.c: set the MTU even though we also specify it in systemd-networkd
for consumption by udev. NetworkManager will try to set it and might
otherwise default to the wrong value.
  * src/networkd.c: Set IPv6AcceptRA=no anytime we don't do DHCPv6 (or by the
same config, SLAAC), and don't have static addresses set. This should fix
the cases where unconfigured devices still get an IPv6 address.
(LP: #1655440)
  * src/nm.c: Explicitly set IPv6 method=ignore when IPv6 is 

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

[Launchpad Bug Tracker]

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 may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

 -- Mathieu Trudel-Lapierre   Thu, 23 Nov 2017
12:30:51 -0500

** Changed in: nplan (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Mathieu Trudel-Lapierre]

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 doesn't always run rules because
  of reconfiguration rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Mathieu Trudel-Lapierre]

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 verification-needed-zesty
** Tags added: verification-done-artful verification-done-xenial 
verification-done-zesty

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Łukasz Zemczak]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed-xenial
** Tags added: verification-needed-xenial

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Łukasz Zemczak]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Artful)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-artful

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Mathieu Trudel-Lapierre]

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 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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Brian Murray]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed-xenial
** Tags added: verification-needed-xenial

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Mathieu Trudel-Lapierre]

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 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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 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
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-xenial to verification-done-xenial. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-xenial. In either case, details of your
> testing will help us make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance!
>
> ** Changed in: nplan (Ubuntu Xenial)
>Status: New => Fix Committed
>
> ** Tags added: verification-needed-xenial
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1669564
>
> Title:
>   udevadm trigger subsystem-match=net doesn't always run rules because
>   of reconfiguration rate-limiting
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/
> 1669564/+subscriptions
>

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Łukasz Zemczak]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Łukasz Zemczak]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Zesty)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-zesty

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Mathieu Trudel-Lapierre]

** 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'
+ Validate that all the changes were correctly applied: netplan apply will run 
'udevadm trigger' for the user, and udev should apply all low-level link 
changes (MTU and renames).
+ Make sure to watch out for device renames on devices that are blacklisted for 
replugging such as mwifiex, etc.
+ 
+ [Regression potential]
+ Verification should watch out for a MTU being set, but set to the wrong 
value, or MTUs being applied to all interfaces rather than just the interface 
for which it was set. Users should also watch out for the network device to be 
renamed correctly, and then seen as the correct name and state in both networkd 
and the ip command. 
+ 
+ ---
+ 
  1. root@ubuntu:~# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04
  
  2. root@ubuntu:~# apt-cache policy udev
  udev:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3. udevadm trigger --verbose --subsystem-match=net --action=add will run and 
read .link files from /run/systemd/network/10-netplan-interface1.link
  and apply MTU settings
  
  4. during system boot running (3) does not set the MTU; running (3)
  after boot has completed MTU is set correctly.
  
  Here'a log during boot where cloud-init generates a netplan config,
- invokes `netplan generate` which writes the networkd config out 
+ invokes `netplan generate` which writes the networkd config out
  and then udevadm trigger (3).  Upon logging in interface1 has an MTU of 1500. 
 Re-running udevadm trigger now runs the rules/link files and updates the MTU.
  
  Note that, if you run udevadm test /sys/class/net/interface1; this also will
  apply the MTU (test probably shouldn't change the interface, I'll file a
  bug for that as well).
  
  # journalctl -o short-precise --no-pager -b | grep WARK
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 
'generate']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', 
'--no-block', 'systemd-udev-trigger.service']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', 
'--verbose', '--subsystem-match=net', '--action=add']:
  
  root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link
  [Match]
  MACAddress=52:54:00:12:34:02
  
  [Link]
  Name=interface1
  WakeOnLan=off
  MTUBytes=1492
  
  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1500
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 35  bytes 3287 (3.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
  root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add
  /sys/devices/pci:00/:00:04.0/virtio1/net/interface1
  /sys/devices/pci:00/:00:05.0/virtio2/net/interface2
    ys/devices/pci:00/:00:06.0/virtio3/net/interface0
  /sys/devices/virtual/net/lo
  
  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1492
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 37  bytes 3504 (3.5 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  2 19:22:14 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  

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

[Łukasz Zemczak]

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 subsystem-match=net doesn't always run rules because
  of reconfiguration rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Launchpad Bug Tracker]

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   Tue, 14 Nov 2017
08:53:51 -0500

** Changed in: nplan (Ubuntu Bionic)
   Status: New => Fix Released

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 in the .link file
> and in Link.MTUBytes key in the .network file.
>
> The .link setting is applied by udev, whereas the .network setting is
> applied by networkd on link up.
>

It used to be that networkd did not apply any MTU values under .network
At the time, it was only applied by .link;  it seems a bit to me like a bug
w.r.t networkd applying
mtu outside of the link; in general it is a property of the device.


> I guess it matters if the link is managed by networkd subsequently or
> not. I wonder if we want to set mtu in .link file, .network, or both.
> Such that mtu is correct if networkd doesn't manage the interface (.link
> file alone), and the mtu is corrected upon link up too (.network
> setting) if it is changed, given that .link files are not.
>

I think it's generally a bug to have the setting in multiple places; that
just can't be
the right thing and smells like it's working around some fundamental issue
with
networkd and udev (which is what consumes the .link files).


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1669564
>
> Title:
>   udevadm trigger subsystem-match=net doesn't always run rules because
>   of reconfiguration rate-limiting
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/
> 1669564/+subscriptions
>

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Dimitri John Ledkov]

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 by udev, whereas the .network setting is
applied by networkd on link up.

I guess it matters if the link is managed by networkd subsequently or
not. I wonder if we want to set mtu in .link file, .network, or both.
Such that mtu is correct if networkd doesn't manage the interface (.link
file alone), and the mtu is corrected upon link up too (.network
setting) if it is changed, given that .link files are not.

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Dimitri John Ledkov]

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 reconfiguration rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Launchpad Bug Tracker]

** 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 doesn't always run rules because
  of reconfiguration rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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

** Also affects: systemd (Ubuntu Bb-series)
   Importance: Undecided
   Status: New

** Also affects: nplan (Ubuntu Bb-series)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: nplan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Artful)
   Importance: High
   Status: Invalid

** Also affects: nplan (Ubuntu Artful)
   Importance: Undecided
   Status: Triaged

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Zesty)

** No longer affects: systemd (Ubuntu Artful)

** No longer affects: systemd (Ubuntu Bb-series)

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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 instruction.

When using the reload then I can confirm that the MTU setting is
applied.  It appears that netplan indeed should run the reload operation
in the 'netplan generate' call.

ubuntu@ubuntu:/$ cat /etc/cloud/build.info 
build_name: server
serial: 20171003
ubuntu@ubuntu:/$ apt-cache policy cloud-init
cloud-init:
  Installed: 17.1-0ubuntu1
  Candidate: 17.1-0ubuntu1
  Version table:
 *** 17.1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu@ubuntu:/$ 
ubuntu@ubuntu:/$ cat /run/systemd/network/*.link
[Match]
MACAddress=52:54:00:12:34:00

[Link]
Name=interface0
WakeOnLan=off
[Match]
MACAddress=52:54:00:12:34:02

[Link]
Name=interface1
WakeOnLan=off
MTUBytes=1492
ubuntu@ubuntu:/$ cat /sys/class/net/interface0/mtu 
1500
ubuntu@ubuntu:/$ cat /sys/class/net/interface1/mtu 
1492
ubuntu@ubuntu:/$ grep udevadm /var/log/cloud-init.log 
2017-10-04 21:05:40,636 - util.py[DEBUG]: Running command ['udevadm', 
'control', '--reload'] with allowed return codes [0] (shell=False, capture=True)
2017-10-04 21:05:40,642 - util.py[DEBUG]: Running command ['udevadm', 
'trigger', '--verbose', '--subsystem-match=net', '--action=add'] with allowed 
return codes [0] (shell=False, capture=True)


** Changed in: nplan (Ubuntu)
   Status: Incomplete => New

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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.

** No longer affects: systemd (Ubuntu Artful)

** No longer affects: nplan (Ubuntu Artful)

** Changed in: systemd (Ubuntu)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

** Changed in: nplan (Ubuntu)
   Status: New => Incomplete

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Francis Ginther]

** 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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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 test case to have: udevadm
control --reload, before calling trigger action and check if this
resolves your issue?

If true, I believe netplan must call udevadm control --reload after
writing out anything that udevd reads, which is udev .rules files and
.link files.

** Also affects: nplan (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Patricia Gaughen]

** 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 doesn't always run rules because
  of reconfiguration rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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 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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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)
   Importance: High
   Status: New

** Tags removed: rls-aa-incoming

-- 
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 rate-limiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs