The attachment "status-wait-flag.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Patch from https://bugs.launchpad.net/ufw/+bug/1923079 which is a dup
** Patch added: "status-wait-flag.patch"
https://bugs.launchpad.net/ufw/+bug/1911637/+attachment/5526213/+files/status-wait-flag.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: ufw
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911637
Title:
Another app is currently holding the xtables lock
To manage notifications about this
Actually, in thinking about this, ufw could use 'iptables -w' under the
hood. I recall having troubles with this approach when providing the fix
for https://bugs.launchpad.net/ufw/+bug/1204579. I suggest following my
advice in my last comment to avoid the issue while using 'iptables -w'
is
Thanks for the report. I read the ansible bug but this issue is actually
coming from the underlying iptables tool. Something on the system is
manipulating the firewall via iptables at the same time that the ufw
command is being run. As described, this would happen with any firewall
software. If
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911637
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911637
Title:
This has been reported on the ansible module side as well as it impacts
the ability to configure ufw on Ubuntu 20.04.02 LTS servers. ufw is
essentially unusable because of this bug.
https://github.com/ansible-collections/community.general/issues/2336