[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-12-11 Thread Launchpad Bug Tracker
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

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-12-11 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-fan - 0.12.8~17.04.1 --- ubuntu-fan (0.12.8~17.04.1) zesty; urgency=medium * fanatic: Optionally provide DNS server for docker test (LP: #1732717) ubuntu-fan (0.12.7~17.04.1) zesty; urgency=medium * fanctl: cmd_up needs to proparate

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-12-11 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-fan - 0.12.8~17.10.1 --- ubuntu-fan (0.12.8~17.10.1) artful; urgency=medium * fanatic: Optionally provide DNS server for docker test (LP: #1732717) ubuntu-fan (0.12.7~17.10.1) artful; urgency=medium * fanctl: cmd_up needs to proparate

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-12-06 Thread Stefan Bader
Verified for Artful/0.12.8~17.10.1 that after an unsuccessful "fanatic enable-fan" run which returned rc=1, the next run with the cause of the failure remove will succeed (before it would not have attempted). ** Tags removed: verification-needed verification-needed-artful ** Tags added:

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-12-06 Thread Stefan Bader
Verified for Zesty/0.12.8~17.04.1 (after failed attempt and releasing lock, next attempt succeeds). ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-12-06 Thread Stefan Bader
Verified for Xenial/0.12.8~16.04.1 that after failing while flock was active, the next attempt after releasing the flock did succeed. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-11-17 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-fan - 0.12.8 --- ubuntu-fan (0.12.8) bionic; urgency=medium * fanatic: Optionally provide DNS server for docker test (LP: #1732717) ubuntu-fan (0.12.7) bionic; urgency=medium * fanctl: cmd_up needs to proparate scan_config errors (LP:

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

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

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-11-07 Thread Łukasz Zemczak
** Also affects: ubuntu-fan (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-10-27 Thread Stefan Bader
** Description changed: SRU Justification (for Artful/Zesty/Xenial): Impact: "fanatic enable-fan" calls to fanctl to actually bring up the Fan bridge. However it is possible that this returns with an error and in that case fanatic must undo previously done configuration changes or

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-10-27 Thread Stefan Bader
** Description changed: SRU Justification (for Artful/Zesty/Xenial): Impact: "fanatic enable-fan" calls to fanctl to actually bring up the Fan bridge. However it is possible that this returns with an error and in that case fanatic must undo previously done configuration changes or

[Bug 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

2017-10-27 Thread Stefan Bader
diff --git a/fanatic b/fanatic index 8366881..5a83ad1 100755 --- a/fanatic +++ b/fanatic @@ -142,7 +142,11 @@ enable_fan() # fi progress "configuring fan underlay:$underlay overlay:$overlay" twiddle_fan_config add "$device" "$overlay" "$underlay" -