Activity log for bug #1027987

Date Who What changed Old value New value Message
2012-07-23 15:14:11 Andreas Ntaflos bug added bug
2012-07-24 15:34:23 Serge Hallyn libvirt (Ubuntu): importance Undecided Medium
2012-07-24 15:34:26 Serge Hallyn libvirt (Ubuntu): status New Confirmed
2012-07-24 18:20:30 Ryan Tandy bug added subscriber Ryan Tandy
2012-07-26 16:13:40 Serge Hallyn nominated for series Ubuntu Precise
2012-07-26 16:13:40 Serge Hallyn bug task added libvirt (Ubuntu Precise)
2012-07-26 16:13:40 Serge Hallyn nominated for series Ubuntu Quantal
2012-07-26 16:13:40 Serge Hallyn bug task added libvirt (Ubuntu Quantal)
2012-07-26 23:10:42 Launchpad Janitor libvirt (Ubuntu Quantal): status Confirmed Fix Released
2012-07-26 23:57:29 Launchpad Janitor branch linked lp:ubuntu/libvirt
2012-09-28 17:34:41 Serge Hallyn attachment added libvirt-timeout.debdiff https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1027987/+attachment/3352663/+files/libvirt-timeout.debdiff
2012-09-28 17:35:27 Serge Hallyn libvirt (Ubuntu Precise): status New Triaged
2012-09-28 17:35:30 Serge Hallyn libvirt (Ubuntu Precise): importance Undecided Medium
2012-10-03 16:55:01 Serge Hallyn description This bug has already been reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers from the same problem. When an LVM-based storage pool is present libvirtd takes around three minutes to start up because a timeout occurs when libvirtd calls "udevadm settle". In the Debian bug report this has been identified as a problem in Libvirt, additional info is found here: http://article.gmane.org/gmane.linux.hotplug.devel/17421 A local workaround is to issue "service udev restart" before starting libvirtd. The bug has been worked around in Debian's Libvirt 0.9.12 by reducing the "udev settle" timeout to ten seconds. Can we expect this workaround to somehow make it into Libvirt 0.9.8 and Ubuntu Precise? ===================================== SRU Justification: 1. Impact: starting libvirtd takes 2 minutes 2. Development fix: in debian and quantal, this is fixed by explicitly giving a shorter timeout when calling udevadm settle. 3. Stable fix: same as development fix 4. Test case: define an lvm based storage pool, then stop and start libvirt. 5. Regression potential: we're lowering a timeout, so in theory the timing of some races could be changed. ===================================== This bug has already been reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers from the same problem. When an LVM-based storage pool is present libvirtd takes around three minutes to start up because a timeout occurs when libvirtd calls "udevadm settle". In the Debian bug report this has been identified as a problem in Libvirt, additional info is found here: http://article.gmane.org/gmane.linux.hotplug.devel/17421  A local workaround is to issue "service udev restart" before starting libvirtd. The bug has been worked around in Debian's Libvirt 0.9.12 by reducing the "udev settle" timeout to ten seconds. Can we expect this workaround to somehow make it into Libvirt 0.9.8 and Ubuntu Precise?
2012-10-03 16:55:08 Serge Hallyn bug added subscriber Ubuntu Stable Release Updates Team
2012-10-18 22:40:32 Brian Murray libvirt (Ubuntu Precise): status Triaged Fix Committed
2012-10-18 22:40:35 Brian Murray bug added subscriber SRU Verification
2012-10-18 22:40:37 Brian Murray tags verification-needed
2012-10-28 05:59:04 Launchpad Janitor branch linked lp:ubuntu/precise-proposed/libvirt
2013-01-11 18:43:33 Brian Murray tags verification-needed verification-done
2013-01-14 12:04:36 Colin Watson removed subscriber Ubuntu Stable Release Updates Team
2013-01-14 12:05:25 Launchpad Janitor libvirt (Ubuntu Precise): status Fix Committed Fix Released