[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ufw (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Won't Fix Status in ufw source package in Disco: Fix Released Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt
This bug was fixed in the package ufw - 0.36-1 --- ufw (0.36-1) unstable; urgency=medium * New upstream release (LP: #1782384, LP: #1664133, LP: #1509725, LP: #1695718, LP: #1719211, LP: #1775043, LP: #1204579, LP: #1652163, LP: #1377600, Closes: 686248, LP: #1368411, LP: #1586258, Closes: 909163, Closes: 884932, LP: #1558068) - drop 0002-bug849628.patch (included upstream) - drop 0003-use-default-tcp-syncookies.patch (included upstream) - drop 0004-lp1633698.patch (included upstream) * Remaining changes: - 0001-optimize-boot.patch * debian/ufw.maintscript: remove /etc/bash_completion.d/ufw on upgrade (LP: #1602834) * debian/control: remove no longer needed xs-python-version and x-python3-version fields * update debian/before6.rules.md5sum for file shipped in 0.35-6. While both before.rules and before6.rules were updated in this new upstream release, 0.35-6 mistakenly already had its own md5sum for before.rules, so we don't need to add it now. -- Jamie Strandboge Fri, 14 Dec 2018 17:50:47 + ** Changed in: ufw (Ubuntu Disco) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Triaged Status in ufw source package in Disco: Fix Released Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt
This will be fixed with the new feature for concurrent updates, which is scheduled for ufw 0.36. ** Changed in: ufw (Ubuntu) Status: Confirmed => In Progress ** Changed in: ufw (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Also affects: ufw (Ubuntu Disco) Importance: Medium Assignee: Jamie Strandboge (jdstrand) Status: In Progress ** Also affects: ufw (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ufw (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: ufw (Ubuntu Bionic) Status: New => Triaged ** Changed in: ufw (Ubuntu Cosmic) Status: New => Triaged ** Changed in: ufw (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ufw (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: In Progress Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Triaged Status in ufw source package in Disco: In Progress Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt
Is there any update on the outlook of this? we are hitting ansible failures due to this bug sometimes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: Confirmed Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt
** Changed in: ufw (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: Confirmed Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377600] Re: ufw errors after ctr+c interupt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ufw (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in “ufw” package in Ubuntu: Confirmed Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
