There is another bug related to ansible in
https://bugs.launchpad.net/ufw/+bug/1911637. I suggest following that
one. Leaving this one as Expired.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921350
[Expired for ufw (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ufw (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921350
Title
Jamie: I was able to reproduce the issue again. I'm thinking the problem
might be related to Ansible, but not 100% sure.
The output of ps auxww|grep ufw is:
root 247851 0.0 0.0 2608 604 pts/1S+ 10:53 0:00 /bin/sh -c
ufw enable ufw allow 22 ufw allow 80 ufw allow 443
root
Jamie: after installing some other things on the server, the problem no
longer exists, so I can't answer the question, unfortunately, nor can I
reproduce this issue. I would say that other ufw commands were not
running because UFW was called via Ansible, but it is not impossible.
Terminating the sc
Thanks you for reporting a bug. Are there other ufw commands running at the
same time? Eg, what is the output of:
$ ps auxww|grep ufw
** Changed in: ufw (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
