[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.40.1~18.04.2

---
netplan.io (0.40.1~18.04.2) bionic; urgency=medium

  * Fix typo breaking rename on 'netplan apply'. (LP: #1770082)

netplan.io (0.40.1~18.04.1) bionic; urgency=medium

  * Backport netplan 0.40.1 to 18.04. (LP: #1793309)

netplan.io (0.40.1) cosmic; urgency=medium

  * tests/generate.py: use random.sample() instead of random.choices() to
better support older pythons.
  * Deal gracefully with empty files on 'netplan apply' (LP: #1795343)

netplan.io (0.40) cosmic; urgency=medium

  * New upstream release:
- networkd: route source is PreferredSource= not From=
- Improve NetworkManager error reporting on unrenderable routes.
- Don't render ipv4 dns-search unless we have an ipv4 address.
  (LP: #1786726)
- Set permissive umask on networkd .network, .link and .netdev files
  (LP: #1736965, LP: #1768560)
- Fix support for link-scope routes. (LP: #1747455)
- Update man pages for deletion of replug code.
- Spell Gratuitous ARP correctly and make it work. (LP: #1756701)
- Many typo fixes for documentation. (LP: #1783940)
- Various build system fixes.
- Fix integration tests:
  - iproute2 output changes for link-scope routes
  - fix stability of networkd igmp-resend test
  - fix manual_addresses test now that networkd lists ~. domain
- Deduplicate code for parsing interface options
- Add support for optional-addresses.

netplan.io (0.39) cosmic; urgency=medium

  * New upstream release:
- Allow link-local addresses to be configured. (LP: #1771704)
- Forces bridges with no addresses to be brought online. (LP: #1736975)

netplan.io (0.38) cosmic; urgency=medium

  * New upstream release:
- Write udev .rules files to /run/udev/rules.d to enforce interface
  renaming. (LP: #1770082)
- Don't traceback for 'netplan ip leases' when iface is not managed or
  doesn't DHCP (LP: #1768823)
- Fix duplicate "/" path separator in error messages (LP: #1771440)
- Fix incorrect terminal reset in 'netplan try' on Ctrl-C. (LP: #1768798)
- Updated doc entries: mtu, fix fwmark->mark, cleanup optional.
  (LP: #1768783)
- Added documentation validation at build.
- Added configuration example for multi-ip interfaces.
  * tests/integration.py: fix test_eth_and_bridge autopkg test harder.
  * debian/control:
- Add iproute2 to Depends.
- Add python3-netifaces to Depends, Build-Depends.

 -- Mathieu Trudel-Lapierre   Mon, 22 Oct 2018
15:02:30 -0400

** Changed in: netplan.io (Ubuntu Bionic)
   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 Released
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
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: 

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Łukasz Zemczak]

Hello Mark, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40~18.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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: netplan.io (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Tags removed: verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
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 Released
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.36.2

---
netplan.io (0.36.2) bionic; urgency=medium

  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
15:33:48 -0400

** Changed in: netplan.io (Ubuntu Bionic)
   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 Released
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~16.04.5

---
nplan (0.32~16.04.5) xenial; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * Do not attempt to rebind driver 'qeth'. (LP: #1756322)
  * Allow setting ClientIdentifier=mac for networkd-renderered devices
(LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
10:36:24 -0400

** Changed in: nplan (Ubuntu Xenial)
   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 Released
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32~17.10.4

---
nplan (0.32~17.10.4) artful; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * debian/postinst: Write breadcrumbs on disk in /etc/network/interfaces to
denote the migration to using netplan. (LP: #1756742)
  * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
with Windows Server-based DHCP servers which don't support RFC 4361.
(LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
11:04:30 -0400

** Changed in: nplan (Ubuntu Artful)
   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 Released
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Mathieu Trudel-Lapierre]

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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.37.1

---
netplan.io (0.37.1) cosmic; urgency=medium

  * tests/integration.py: fix autopkgtests to be less flaky, especially given
changes in systemd-networkd's behavior regarding Router Advertisements.

 -- Mathieu Trudel-Lapierre   Fri, 11 May 2018
09:58:19 -0400

** Changed in: netplan.io (Ubuntu)
   Status: In Progress => 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 Committed
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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756587] Re: mii-mon should have a consistent unit schema

[Mathieu Trudel-Lapierre]

Updating the bug tags to make it clear where we've landed this and where
it hasn't been fixed yet, given the rename of nplan -> netplan.io in
bionic.

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

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

** Also affects: netplan.io (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: netplan.io (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: netplan.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: netplan.io (Ubuntu Artful)
   Status: New => Invalid

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

-- 
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 Committed
Status in netplan.io package in Ubuntu:
  In Progress
Status in nplan package in Ubuntu:
  Invalid
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  New
Status in netplan.io source package in Bionic:
  New
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 : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp