Activity log for bug #1245322

Date Who What changed Old value New value Message
2013-10-28 03:45:45 Claude Durocher bug added bug
2013-10-28 15:45:36 Serge Hallyn bug task added ufw
2013-10-29 16:57:15 Serge Hallyn libvirt (Ubuntu): importance Undecided Medium
2013-10-29 16:57:15 Serge Hallyn libvirt (Ubuntu): status New Confirmed
2013-10-30 18:00:15 Serge Hallyn nominated for series Ubuntu Saucy
2013-10-30 18:00:15 Serge Hallyn bug task added libvirt (Ubuntu Saucy)
2013-10-31 21:38:04 Serge Hallyn attachment added libvirt-xtables.debdiff https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1245322/+attachment/3897104/+files/libvirt-xtables.debdiff
2013-11-01 00:19:43 Ubuntu Foundations Team Bug Bot tags patch
2013-11-04 14:50:44 Jamie Strandboge bug task deleted ufw
2013-11-14 09:29:13 Launchpad Janitor libvirt (Ubuntu): status Confirmed Fix Released
2013-11-14 16:48:03 Serge Hallyn description Running KVM under Ubuntu 13.10 64 bits. When UFW is enabled, the default network won't start automatically when set to do so. Manual startup of the network must be done before starting the first guest. Error in /var/log/libvirt/libvirtd.log when UFW is enabled : 2013-10-28 02:53:31.732+0000: 1485: error : virCommandWait:2348 : internal error: Child process (/sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 4: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? 2013-10-28 02:53:31.732+0000: 1485: error : networkAddGeneralFirewallRules:1895 : failed to add iptables rule to allow DHCP requests from 'virbr0' Disabling UFW and rebooting solves the issue (default network is started automatically). This behaviour is new in 13.10 (it was working fine in 13.04 and before). ============================================ SRU justification ============================================ 1. Impact: libvirt may fail to start 2. Development fix: have libvirt use -w flag to iptables to have it wait rather than fail on lock contention 3. Stable fix: same as dev fix 4. Test case: install ufw and libvirt; reboot a few times. 5. Regression potential: there should be none, this only passes the -w flag to iptables if it is supported. Running KVM under Ubuntu 13.10 64 bits. =================================================== When UFW is enabled, the default network won't start automatically when set to do so. Manual startup of the network must be done before starting the first guest. Error in /var/log/libvirt/libvirtd.log when UFW is enabled : 2013-10-28 02:53:31.732+0000: 1485: error : virCommandWait:2348 : internal error: Child process (/sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 4: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? 2013-10-28 02:53:31.732+0000: 1485: error : networkAddGeneralFirewallRules:1895 : failed to add iptables rule to allow DHCP requests from 'virbr0' Disabling UFW and rebooting solves the issue (default network is started automatically). This behaviour is new in 13.10 (it was working fine in 13.04 and before).
2013-11-14 16:48:11 Serge Hallyn libvirt (Ubuntu Saucy): status New Triaged
2013-11-14 16:48:17 Serge Hallyn libvirt (Ubuntu Saucy): importance Undecided High
2013-11-14 16:48:20 Serge Hallyn libvirt (Ubuntu): importance Medium High
2013-11-14 18:40:05 Brian Murray libvirt (Ubuntu Saucy): status Triaged Fix Committed
2013-11-14 18:40:06 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2013-11-14 18:40:09 Brian Murray bug added subscriber SRU Verification
2013-11-14 18:40:11 Brian Murray tags patch patch verification-needed
2013-11-15 15:58:11 Claude Durocher tags patch verification-needed patch verification-done
2013-11-26 19:18:02 Stéphane Graber removed subscriber Ubuntu Stable Release Updates Team
2013-11-26 19:23:12 Launchpad Janitor libvirt (Ubuntu Saucy): status Fix Committed Fix Released