Activity log for bug #1745597

Date Who What changed Old value New value Message
2018-01-26 11:32:23 Chris Jones bug added bug
2018-01-26 17:01:47 Ryan Harper netplan: status New Confirmed
2018-01-26 17:37:04 Mathieu Trudel-Lapierre netplan: status Confirmed Triaged
2018-01-26 17:37:07 Mathieu Trudel-Lapierre netplan: importance Undecided High
2018-01-26 17:37:10 Mathieu Trudel-Lapierre netplan: assignee Mathieu Trudel-Lapierre (cyphermox)
2018-01-26 17:38:34 Launchpad Janitor merge proposal linked https://code.launchpad.net/~raharper/netplan/+git/netplan/+merge/336717
2018-04-13 12:34:42 Francis Ginther tags id-5acf94da4fdc30917ec9c571
2018-04-17 16:58:38 Mathieu Trudel-Lapierre netplan: status Triaged In Progress
2018-04-22 18:58:42 Mike Pastore bug added subscriber Mike Pastore
2018-04-30 13:48:05 Mathieu Trudel-Lapierre marked as duplicate 1765833
2018-04-30 14:15:17 Mathieu Trudel-Lapierre removed duplicate marker 1765833
2018-04-30 14:15:34 Mathieu Trudel-Lapierre bug task added nplan (Ubuntu)
2018-04-30 14:15:44 Mathieu Trudel-Lapierre nplan (Ubuntu): status New Fix Released
2018-04-30 14:15:51 Mathieu Trudel-Lapierre netplan: status In Progress Fix Released
2018-04-30 14:16:00 Mathieu Trudel-Lapierre nominated for series Ubuntu Artful
2018-04-30 14:16:00 Mathieu Trudel-Lapierre bug task added nplan (Ubuntu Artful)
2018-04-30 14:16:00 Mathieu Trudel-Lapierre nominated for series Ubuntu Xenial
2018-04-30 14:16:00 Mathieu Trudel-Lapierre bug task added nplan (Ubuntu Xenial)
2018-04-30 14:28:32 Mathieu Trudel-Lapierre description The manpage for netplan doesn't indicate what the unit for mii-monitor-interval is on bond devices. It appears to be in whole seconds, but at the kernel level, the unit is milliseconds. From my testing, it appears to be impossible to set a value for mii-monitor-interval with netplan that is <1s (e.g. I got a syntax error with a value of 0.1 for 100ms) [Impact] Users of bond and bridges devices requiring tuning of the default device parameters. [Test case] == Configure MII monitor interval == 1) Configure a bond device 2) Add parameters: bonds: mybond0: parameters: mii-monitor-interval: 1 3) Verify that the applied MII monitor interval is of 1ms, as opposed to 1 second (1000ms), by verifying the contents of /sys/class/net/mybond0/bonding/miimon == Validate default behavior == 1) Configure a bond device without parameters. 2) Verify that no special MII monitor interval is applied, the default value should be 0: $ cat /sys/class/net/mybond0/bonding/miimon 0 [Regression potential] MII monitor behavior is changing with this SRU. Default behavior for an unqualified value (ie. a number alone), which was also the only way to specify parameters, was to interpret the values as *seconds*. This leads to relatively slow checking of the device link status (for MII monitor), much slower than generally expected. The same applies to other time-based values such as up delay, down delay, arp interval. The interpretation for these values changes to reading them as *milliseconds* when unqualified, and a new way of qualifying the values (adding a modifier) was added. This was, people who do require "slow" checking of the MII link status will be migrated to "fast" checking right now, moving from an interval of 1 second to 1 millisecond (more checking means less false-negatives for packet passing through an interface, should reduce packet loss, at the cost of potentially flapping the interfaces (bringing down a path often if MII status is bad or slow to be returned)). Users who require the old behavior may add "s" at the end of the value to make it read as "1 second" again, or modify the value to be "1000", which will be 1000ms (1 second). We estimate the impact of this change to users to be minimal, actually requiring a 1 second interval for MII monitoring / up/down delay, and ARP interval is very uncommon and counter-intuitive as all other systems work on a millisecond basis. --- The manpage for netplan doesn't indicate what the unit for mii-monitor-interval is on bond devices. It appears to be in whole seconds, but at the kernel level, the unit is milliseconds. From my testing, it appears to be impossible to set a value for mii-monitor-interval with netplan that is <1s (e.g. I got a syntax error with a value of 0.1 for 100ms)
2018-05-08 20:49:39 Brian Murray nplan (Ubuntu Artful): status New Fix Committed
2018-05-08 20:49:42 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2018-05-08 20:49:45 Brian Murray bug added subscriber SRU Verification
2018-05-08 20:49:50 Brian Murray tags id-5acf94da4fdc30917ec9c571 id-5acf94da4fdc30917ec9c571 verification-needed verification-needed-artful
2018-05-08 21:09:27 Brian Murray nplan (Ubuntu Xenial): status New Fix Committed
2018-05-08 21:09:35 Brian Murray tags id-5acf94da4fdc30917ec9c571 verification-needed verification-needed-artful id-5acf94da4fdc30917ec9c571 verification-needed verification-needed-artful verification-needed-xenial
2018-05-14 20:49:03 Mathieu Trudel-Lapierre tags id-5acf94da4fdc30917ec9c571 verification-needed verification-needed-artful verification-needed-xenial id-5acf94da4fdc30917ec9c571 verification-done-artful verification-needed verification-needed-xenial
2018-05-15 15:16:22 Mathieu Trudel-Lapierre tags id-5acf94da4fdc30917ec9c571 verification-done-artful verification-needed verification-needed-xenial id-5acf94da4fdc30917ec9c571 verification-done-artful verification-done-xenial
2018-06-06 01:09:38 Launchpad Janitor nplan (Ubuntu Artful): status Fix Committed Fix Released
2018-06-06 01:10:03 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2018-06-06 01:10:38 Launchpad Janitor nplan (Ubuntu Xenial): status Fix Committed Fix Released
2019-04-01 14:07:00 Janåke Rönnblom bug added subscriber Janåke Rönnblom