RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
libvirt should change to use iptables and ebtabels after stop firewalld when libvirtd is running

Version-Release number of selected component (if applicable):
libvirt-1.2.8-16.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.start firewalld and restart libvirtd:
# service firewalld start
Redirecting to /bin/systemctl start  firewalld.service

# service libvirtd restart
Redirecting to /bin/systemctl restart  libvirtd.service

2.stop firewalld when libvirtd is running
# service firewalld stop
Redirecting to /bin/systemctl stop  firewalld.service

3.check the libvirtd log:
2015-02-02 02:40:52.074+0000: 4262: error : virFirewallApplyRuleFirewallD:758 : internal error: Unable to apply rule 'The name org.fedoraproject.FirewallD1 was not provided by any .service files'

4.try to start a vm have nwfilter settings:
# virsh start test4
error: Failed to start domain test4
error: internal error: Unable to apply rule 'The name org.fedoraproject.FirewallD1 was not provided by any .service files'


Actual results:
libvirtd still try to use firewalld when firewalld is stop

Expected results:
dynamic change the currentBackend when FirewallD NameOwnerChanged (firewalld start/stop).

Additional info:

No, we really don't want to dynamically change the firewall backend. When you see Firewalld name disappear from DBus, it is not reasonable to assume the admin wants to stop using it. The name could be disappearing because the firewalld service is being restarted for some reason. If we try to fallback to plain iptables and firewalld starts again, it will cause us no end of pain. It is not common practice to change between firewalld & iptables on a host - it is something an admin will typically decide once when provisioning the host and not change after that, so optimizing for this one time only change of decision is not a good idea.