Hide Forgot
Description of problem: due to https://bugzilla.redhat.com/show_bug.cgi?id=692558 its possible to have libvirt installed w/o ipforwarding enabled. Since we depend on it for builds now, its probably a good idea to check for it w/ the puppet scripts. [root@dell-pe2950-01 ~]# cat /proc/sys/net/ipv4/ip_forward 1 found in.. root@dhcp231-29 ~]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.0.3-0.fc14.20110331142542gitfcf7990.x86_64 aeolus-configure-2.0.0-5.fc14.20110330155142gitecf8f95.noarch aeolus-conductor-0.0.3-0.fc14.20110331142542gitfcf7990.x86_64 aeolus-conductor-doc-0.0.3-0.fc14.20110331142542gitfcf7990.x86_64 [root@dhcp231-29 ~]#
IMHO we should bail out of the configure script if its not set to 1. I doubt we want to configure that for a user.
While doing this check during configure time is not a bad idea, it unfortunately doesn't really prevent the issue. Other process (NetworkManager comes to mind) can and do write to /proc/sys/net/ipv4/ip_forward of their own accord. What could happen then is that we could check, everything could be fine, and then NetworkManager could come along and undo it. This is unfortunately not something we can easily fix at our layer. It is also unfortunately not something that is fixed in later libvirt (at least, not yet). So we are sort of in a tough situation here. Chris Lalancette
perm close