group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1672740@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nplan - 0.23~16.04.1

---------------
nplan (0.23~16.04.1) xenial; urgency=medium

  * Backport netplan 0.23 to 16.04. (LP: #1688632)

nplan (0.23) artful; urgency=medium

  * Do not unbind brcmfmac, interface will be gone. (LP: #1696162)

nplan (0.22) artful; urgency=medium

  * Add support for setting a custom MAC address on all device types.
    (LP: #1690388)
  * Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
    changes.

nplan (0.21) artful; urgency=medium

  [ Ryan Harper ]
  * Add support for setting MTU on a device. (LP: #1668693)

  [ Mathieu Trudel-Lapierre ]
  * Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
  * debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
    Both ship the same /usr/sbin/netplan. (LP: #1665842)

nplan (0.20) zesty; urgency=medium

  * tests/integration.py: increase timeout for integration tests (networkd and
    NetworkManager "wait-online" checks) to account for longer bring-up times
    when dealing with stacked virtual devices.

nplan (0.19) zesty; urgency=medium

  * Add support for unordered definition of network devices: you can now
    specify a virtual devices before their member devices. (LP: #1670495)
  * Allow setting up the STP state for a bridge. (LP: #1665088)
  * Document bond/bridge parameters support. (LP: #1664702)

nplan (0.18) zesty; urgency=medium

  * debian/tests/integration.py: in some cases 'iw reg get' may qualify the
    reg domain results with 'global'; we must not let that trip up tests when
    they are run on Ubuntu infrastructure vs. local tests.

nplan (0.17) zesty; urgency=medium

  * New release:
    - Add support for configuring bonds.
    - Add support for configuring bridges.

nplan (0.16) zesty; urgency=medium

  [ Martin Pitt ]
  * doc/example-config: Adjust "routes:" example.
    It does not make sense to make "routes:" a global thing, they should be
    tied to an interface so that the route is only set when the corresponding
    interface exists and is up, and the config is not split in two parts.
  * doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)

  [ Mathieu Trudel-Lapierre ]
  * Fix coverage for src/netplan to be 100%, and fail if coverage falls below
    that mark again.
  * Add support for specifying routes.

nplan (0.15) zesty; urgency=medium

  * tests/generate.py: Fix PEP-8 error (newly detected by -proposed
    pycodestyle).

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Tue, 06 Jun 2017
17:19:10 -0700

** 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/1672740

Title:
  Netplan replug function is incompatible with ath9k_htc module

Status in netplan:
  Fix Released
Status in Snappy:
  New
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Yakkety:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Replugging ath9k_htc may confuse the driver and cause connection issues.

  [Test case]
  - Run nplan integration tests on the release
  - Validate that netplan generate && netplan apply alone, without config, behave as expected (no result)
  - Validate that netplan generate && netplan apply with minimal config writes /run/NetworkManager/conf.d/10-globally-managed-devices.conf
  - Validate that netplan generate && netplan apply works with any existing configuation.

  - Run 'netplan apply' with a valid config for an ath9k_htc device,
  validate the device is not replugged.

  [Regression potential]
  Existing configurations that do not rely on ath9k, brcmfmac or mwifiex (for example) should continue to replug the devices where appropriate to ensure the interface renaming is correctly applied. Configurations for the affected devices should not fail to apply supported configuration.

  ---

  We hit the following problem about the interaction  between netplan
  and the ath9k_htc module, controlling the chip Atheros AR9271.

  If you run the following command

      netplan --debug apply

  or  you use console-conf for setting the network interfaces we get the
  following messages :

  ** (generate:2261): DEBUG: Processing input file //etc/netplan/00-snapd-config.yaml..
  ** (generate:2261): DEBUG: eth0: setting default backend to 1
  ** (generate:2261): DEBUG: Generating output files..
  ** (generate:2261): DEBUG: NetworkManager: definition eth0 is not for us (backend 1)
  DEBUG:netplan generated networkd configuration exists, restarting networkd
  DEBUG:no netplan generated NM configuration exists
  DEBUG:device lo operstate is unknown, not replugging
  DEBUG:device eth0 operstate is up, not replugging
  DEBUG:replug wlan0: unbinding 4-1:1.0 from /sys/bus/usb/drivers/ath9k_htc
  DEBUG:replug wlan0: rebinding 4-1:1.0 to /sys/bus/usb/drivers/ath9k_htc

  The last two row show two consecutive actions, one soon after the
  other:  unbind and bind the usb device on usb hub.

  The module ath9k_htc doesn't work fine in this situation: the wireless
  interface disappears.

  Our problem can be fixed by using the same approach used for mac80211_hwsim e mwifiex_pcie modules.
  The attached patch file fix the issue following the same pattern adopted for the following modules:
  mwifiex_pcie,mac80211_hwsim.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1672740/+subscriptions