I can confirm that this bug also affects *some* of our desktops running
18.04. I haven't figured out why it didn't affect all (100+) machines.
Here is the status output of firewalld service running on a hostname
'matht335':
```
# systemctl status firewalld
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firewalld (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/1835188
Title:
That code path fails to detect that neither --wait or -w is supported, since
iptables-restore returns a successful return code on invalid parameters and
firewalld uses the return code to detect whether it works:
# echo "#foo" | /sbin/iptables-restore --wadit=2; echo $?
/sbin/iptables-restore: unr
Mostly when firewalld fails with that error, a restart will fix it (It
seems to only hit that code path sometimes), however if it is a headless
box, that restart might be tricky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
