[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

This bug was fixed in the package ubuntu-fan - 0.12.8~16.04.1 --- ubuntu-fan (0.12.8~16.04.1) xenial; urgency=medium * fanatic: Optionally provide DNS server for docker test (LP: #1732717) ubuntu-fan (0.12.7~16.04.1) xenial; urgency=medium * fanctl: cmd_up needs to proparate

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

dpkg -l|grep fan ii ubuntu-fan 0.12.8~16.04.1 all Ubuntu FAN network support enablement ip address show ens8 3: ens8: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

Hello Stefan, or anyone else affected, Accepted ubuntu-fan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- fan/0.12.7~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

This bug was fixed in the package ubuntu-fan - 0.12.4~17.04.1 --- ubuntu-fan (0.12.4~17.04.1) zesty; urgency=medium [ Andy Whitcroft ] * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610) * fanctl: correctly specify local interface specific config (LP:

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

Verified that upgrading to 0.12.4~17.04.1 allows to enable a Fan Bridge using an underlay of 192.168.122.0/24 (this failed with the current version). Manually ran both docker and LXD self-test. The commented out debug echos are actually deliberate to be enabled if in need. ** Tags removed:

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

In some of the changes for fanctl I see a lot of commented-out debugging 'echo' statements. Maybe it would be nice to get those cleaned up with one day for all releases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

Hello Stefan, or anyone else affected, Accepted ubuntu-fan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- fan/0.12.4~17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

** Changed in: ubuntu-fan (Ubuntu Zesty) Status: Incomplete => In Progress ** Changed in: ubuntu-fan (Ubuntu Xenial) Status: New => Triaged ** Changed in: ubuntu-fan (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu Xenial) Importance:

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

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

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

The SRU information in the bug description is missing a "Regression Potential" section. ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu.

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

This bug was fixed in the package ubuntu-fan - 0.12.4 --- ubuntu-fan (0.12.4) artful; urgency=medium [ Andy Whitcroft ] * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610) * fanctl: correctly specify local interface specific config (LP: #1707610) *

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

This is occuring because fanatic is trying to bring up the newly configured Fan Network as if it had been brought up automatically. This is done to bring the system into a state that is equivalent to having had the configuration for this Fan Network at boot time. However it does it using an

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

We actually only want to bring up enabled Fan Networks, fanatic is indicating this via its use of --auto. Use this to modify the config scanner. Does the attached (untested) patch help. ** Patch added: "0001-fanctl-only-bring-up-enabled-Fan-Networks-in-auto-mo.patch"

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

** Changed in: ubuntu-fan (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

** Tags added: patch -- 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: New Bug

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

** Patch added: "0001-fanctl-config_scan-stop-after-successful-run.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+attachment/4924595/+files/0001-fanctl-config_scan-stop-after-successful-run.patch -- You received this bug notification because you are a member of