This is fixed in current Ubuntu 21.04.
I dropped our hacks in our projects: https://github.com/cockpit-
project/cockpit-machines/pull/465 and https://github.com/cockpit-
project/bots/pull/2676
** Changed in: firewalld (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug no
This somehow does not affect Ubuntu 20.04 LTS, but it does affect the
current "groovy" release again:
# virsh net-start default
error: Failed to start network default
error: internal error: firewalld is set to use the nftables backend, but the
required firewalld 'libvirt' zone is missing. Either
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/1799095
Title:
I did not tried but it seems to be the way to go ?
"If firewalld is active on the host, libvirt will attempt to place the
bridge interface of a libvirt virtual network into the firewalld zone
named "libvirt" (thus making all guest->host traffic on that network
subject to the rules of the "libvirt"
FTR, the default backend has been reverted to iptables in last uploads
of firewalld
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799095
Title:
Firewalld nftables backend breaks networking of libvi
