** Description changed:

  SRU Justification (Zesty/Xenial)
  
  Impact: When /etc/network/fan contains two entries for the same mapping
  (for example on mapping for the generic network mapping and one for a
  specific interface) it will try to set up the same Fan bridge twice.
  
- Fix: Add a break which exits the setup loop once there has been one
- successful run.
+ Fix: Modify fanctl to only bring up enabled networks in auto mode and to
+ correctly apply the most specific local configuration.
  
  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
-  fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
+  fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.
+ 
+ Regression Potential: We tested both cases of using an underlay/overlay
+ combination which is in the template section and one that was using a
+ subset for the underlay. The former was working before the latter not.
+ For that reason we anticipate a low risk of regression.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1707610

Title:
  fanctl does not stop setup on first match

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  Incomplete

Bug description:
  SRU Justification (Zesty/Xenial)

  Impact: When /etc/network/fan contains two entries for the same
  mapping (for example on mapping for the generic network mapping and
  one for a specific interface) it will try to set up the same Fan
  bridge twice.

  Fix: Modify fanctl to only bring up enabled networks in auto mode and
  to correctly apply the most specific local configuration.

  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
   fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.

  Regression Potential: We tested both cases of using an
  underlay/overlay combination which is in the template section and one
  that was using a subset for the underlay. The former was working
  before the latter not. For that reason we anticipate a low risk of
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to