Verification-done on bionic: netplan.io 0.36.2
Verification-done on artful: nplan 0.32~17.10.4
Verification-done on xenial: nplan 0.32~16.04.5
The updated documentation is available in the SRU'ed packages:
"""
[...] Unless otherwise specified, parameter values for time intervals should be
expressed in milliseconds, but can also be expressed in seconds using a time
suffix (such as "s" for seconds, "ms" for milliseconds).
"""
"""
forward-delay (scalar)
Specify the period of time (in seconds) the bridge will
remain in Listening and Learning states before getting to the
Forwarding state. This field maps to the ForwardDelaySec=
property for the networkd renderer.
"""
** Tags removed: verification-needed verification-needed-artful
verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-artful verification-done-bionic
verification-done-xenial
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756587
Title:
mii-mon should have a consistent unit schema
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Invalid
Status in netplan.io source package in Xenial:
Invalid
Status in nplan source package in Xenial:
Fix Committed
Status in netplan.io source package in Artful:
Invalid
Status in nplan source package in Artful:
Fix Committed
Status in netplan.io source package in Bionic:
Fix Committed
Status in nplan source package in Bionic:
Invalid
Bug description:
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1756587/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : [email protected]
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
