Description of problem: Because of its use of lokkit to change iptables configuration, libvirt clobbers manual changes to /etc/sysconfig/iptables; this is particularly bad, since it will clobber those changes even if lokkit/system-config-firewall have never been used on the system. Version-Release number of selected component (if applicable): libvirt-0.4.2-3.fc9 The libvirt/lokkit integration issue is tracked as https://bugzilla.redhat.com/show_bug.cgi?id=227011
bug #443796 is where we originally enabled lokkit support The issue is: - libvirt makes sure its iptables rules aren't lost when changes are made using s-c-fw, or when iptables is restarted, by using lokkit --with-custom-rules - unfortunately (and this is what was unforseen), lokkit will clobber any manual changes a user has made to /etc/sysconfig/iptables - usually these manual changes would only be clobbered if the user used s-c-fw (or similar), but now they are clobber merely by installing libvirt - the original iptables patch proposed in bug #227011 wouldn't have had this problem Clearly this is a regression - users who had manually set up iptables rules will get their working setup busted by installing libvirt. I'm going to go ahead and push an F-9 and rawhide update removing lokkit support.
See also #447633 - lokkit support wasn't working with selinux enabled
Fixed with: * Wed Jun 4 2008 Mark McLoughlin <markmc> - 0.4.2-4.fc9 - Disable lokkit support again (#449996, #447633) - Ensure PolicyKit is enabled (#446616)
Use "lokkit --disabled" and lokkit will not touch the firewall configuration files anymore. This is and was the way lokkit behaves since some years.
libvirt-0.4.2-4.fc9 has been submitted as an update for Fedora 9