** Description changed: + [Impact] + Documentation is confusing to users wishing to tune bond and bridge parameters. This potentially affects all users of netplan. + + + [Test case] + 1) Update the netplan.io package. + 2) Run 'man netplan' + 3) Verify that the documentation under "parameters" for bridges and bonds is clear that time-based parameters are in milliseconds unless otherwise specified by the individual parameter: + + For example, in the bonds section: + - learn-packet-interval is in seconds + - mii-monitor-interval, up-delay, down-delay, arp-interval are in milliseconds + + + [Regression potential] + Change is limited to the manpage; there is no risk of regression there, except for a garbled manpage or missing file. Any new bugs in netplan behavior found after this SRU that can't be reproduced with the immediately previous version should be investigated as potential toolchain / build issues introduced by the new build required for the SRU. + + --- + The docs say "Using the NetworkManager renderer, parameter values for intervals should be expressed in milliseconds; for the systemd renderer, they should be in seconds unless otherwise specified." This however fails to encapsulate the description of the network in a form abstracted from the renderer. We should have a scheme which is clear, has one and only one explicit form, and works with all renderers.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756587 Title: mii-mon should have a consistent unit schema To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1756587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
