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 : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
