Activity log for bug #986973

Date Who What changed Old value New value Message
2012-04-22 19:16:12 Jared Biel bug added bug
2012-04-23 08:33:00 Robie Basak bug task added facter
2012-04-23 08:46:23 Robie Basak bug task deleted facter
2012-04-23 08:48:12 Robie Basak facter (Ubuntu): status New Triaged
2012-04-23 08:48:43 Robie Basak facter (Ubuntu): importance Undecided Medium
2012-04-23 08:48:51 Robie Basak bug added subscriber Robie Basak
2012-04-24 15:36:34 Marc Cluet bug added subscriber Marc Cluet
2012-04-25 09:05:47 Marc Cluet facter (Ubuntu): assignee Marc Cluet (lynxman)
2012-04-25 09:18:15 James Page nominated for series Ubuntu Precise
2012-04-25 09:18:15 James Page bug task added facter (Ubuntu Precise)
2012-04-25 09:18:15 James Page nominated for series Ubuntu Quantal
2012-04-25 09:18:15 James Page bug task added facter (Ubuntu Quantal)
2012-04-25 09:18:23 James Page facter (Ubuntu Precise): status Triaged Won't Fix
2012-04-25 09:18:27 James Page facter (Ubuntu Quantal): status New Triaged
2012-04-25 09:18:29 James Page facter (Ubuntu Quantal): importance Undecided Medium
2012-09-03 08:29:17 James Page facter (Ubuntu Quantal): status Triaged Won't Fix
2012-09-03 08:29:22 James Page nominated for series Ubuntu R-series
2012-09-03 08:29:22 James Page bug task added facter (Ubuntu R-series)
2012-09-03 08:29:28 James Page facter (Ubuntu R-series): status New Triaged
2012-09-03 08:29:32 James Page facter (Ubuntu R-series): importance Undecided Medium
2012-09-03 08:29:47 James Page bug task deleted facter (Ubuntu R-series)
2012-09-03 08:30:00 James Page facter (Ubuntu): assignee Marc Cluet (lynxman)
2012-10-10 19:55:34 Shane Meyers bug added subscriber Shane Meyers
2013-06-11 16:34:09 Robie Basak summary Facter bug causes puppet to become a zombie Facter bug causes puppet to freeze
2013-06-11 16:34:18 Robie Basak summary Facter bug causes puppet to freeze Facter bug causes puppet to hang
2013-06-11 17:38:20 Don MacAskill bug added subscriber Don MacAskill
2013-06-13 08:16:41 Robie Basak facter (Ubuntu Precise): assignee Marc Cluet (lynxman)
2013-06-13 08:16:45 Robie Basak facter (Ubuntu Precise): status Won't Fix New
2013-06-28 09:21:47 Robie Basak facter (Ubuntu Precise): assignee Robie Basak (racb)
2013-07-02 03:04:36 Robie Basak description I found a bug with Facter that's affecting the version distributed with 12.04. Upstream bug report here: http://projects.puppetlabs.com/issues/12723 This makes puppet completely unusable for us unless this change is applied. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: facter 1.6.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-virtual 3.2.14 Uname: Linux 3.2.0-23-virtual x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 19:11:56 2012 Ec2AMI: ami-2616cd4f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: c1.medium Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: facter UpgradeStatus: No upgrade log present (probably fresh install) [Impact] "puppet apply" hangs about 20% of the time on affected servers. This affects users using puppet without a puppetmaster. The normal use case is to make "puppet apply" run regularly. This causes hung puppet processes to build up, eventually exhausting system resources. For those users using puppet without a puppetmaster, this makes puppet unusable. [Workaround] Run puppet with the timeout command. For example: timeout -k 300s 290s puppet apply /etc/puppet/manifests/site.pp [Development Fix] Fixed upstream by removing some unnecessary thread-exclusive locks that were evidently causing a deadlock when the facter module is used from puppet in the "puppet apply" case. [Stable Fix] Development fix cherry-picked from upstream. [Test Case] 1. apt-get install -y puppet 2. cat > /etc/puppet/manifests/site.pp <<EOT file { '/tmp/foo': content => 'bar'; } EOT 3. successes=0; failures=0; for i in `seq 1 100`; do timeout -k 35s 30s puppet apply /etc/puppet/manifests/site.pp; rv=$?; echo "Exit status $rv"; if [ $rv -eq 0 ]; then successes=$(($successes+1)); else failures=$(($failures+1)); fi; done; echo "Successses: $successes; failures: $failures" Expected result: Successes: 100; failures: 0 Actual result (approx): Successes: 80; failures: 20 Note that this is dependent on a race condition, so this is difficult to reproduce. I have not managed to reproduce the fault reliably except on particular servers where it happens to occur. I have a server where it is happening, and the fix eliminates the problem, and am prepared to use this for -proposed verification. [Regression Potential] The code that runs inside each lock section is trivial, clearly does not need a lock, and upstream concurs: http://projects.puppetlabs.com/issues/12723 [Original Description] I found a bug with Facter that's affecting the version distributed with 12.04. Upstream bug report here: http://projects.puppetlabs.com/issues/12723 This makes puppet completely unusable for us unless this change is applied. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: facter 1.6.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-virtual 3.2.14 Uname: Linux 3.2.0-23-virtual x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 19:11:56 2012 Ec2AMI: ami-2616cd4f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: c1.medium Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron:  LC_CTYPE=en_US.UTF-8  TERM=xterm  LANG=en_US.UTF-8  SHELL=/usr/bin/zsh SourcePackage: facter UpgradeStatus: No upgrade log present (probably fresh install)
2013-07-02 03:05:10 Robie Basak facter (Ubuntu Precise): status New In Progress
2013-07-02 03:05:20 Robie Basak facter (Ubuntu): status Triaged Fix Released
2013-07-02 03:56:23 Robie Basak description [Impact] "puppet apply" hangs about 20% of the time on affected servers. This affects users using puppet without a puppetmaster. The normal use case is to make "puppet apply" run regularly. This causes hung puppet processes to build up, eventually exhausting system resources. For those users using puppet without a puppetmaster, this makes puppet unusable. [Workaround] Run puppet with the timeout command. For example: timeout -k 300s 290s puppet apply /etc/puppet/manifests/site.pp [Development Fix] Fixed upstream by removing some unnecessary thread-exclusive locks that were evidently causing a deadlock when the facter module is used from puppet in the "puppet apply" case. [Stable Fix] Development fix cherry-picked from upstream. [Test Case] 1. apt-get install -y puppet 2. cat > /etc/puppet/manifests/site.pp <<EOT file { '/tmp/foo': content => 'bar'; } EOT 3. successes=0; failures=0; for i in `seq 1 100`; do timeout -k 35s 30s puppet apply /etc/puppet/manifests/site.pp; rv=$?; echo "Exit status $rv"; if [ $rv -eq 0 ]; then successes=$(($successes+1)); else failures=$(($failures+1)); fi; done; echo "Successses: $successes; failures: $failures" Expected result: Successes: 100; failures: 0 Actual result (approx): Successes: 80; failures: 20 Note that this is dependent on a race condition, so this is difficult to reproduce. I have not managed to reproduce the fault reliably except on particular servers where it happens to occur. I have a server where it is happening, and the fix eliminates the problem, and am prepared to use this for -proposed verification. [Regression Potential] The code that runs inside each lock section is trivial, clearly does not need a lock, and upstream concurs: http://projects.puppetlabs.com/issues/12723 [Original Description] I found a bug with Facter that's affecting the version distributed with 12.04. Upstream bug report here: http://projects.puppetlabs.com/issues/12723 This makes puppet completely unusable for us unless this change is applied. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: facter 1.6.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-virtual 3.2.14 Uname: Linux 3.2.0-23-virtual x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 19:11:56 2012 Ec2AMI: ami-2616cd4f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: c1.medium Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron:  LC_CTYPE=en_US.UTF-8  TERM=xterm  LANG=en_US.UTF-8  SHELL=/usr/bin/zsh SourcePackage: facter UpgradeStatus: No upgrade log present (probably fresh install) [Impact] "puppet apply" hangs about 20% of the time on affected servers. This affects users using puppet without a puppetmaster. The normal use case is to make "puppet apply" run regularly. This causes hung puppet processes to build up, eventually exhausting system resources. For those users using puppet without a puppetmaster, this makes puppet unusable. [Workaround] Run puppet with the timeout command. For example:      timeout -k 300s 290s puppet apply /etc/puppet/manifests/site.pp This assumes that there won't be another hang on the next run. This is useful if you run "puppet apply" from a cron job, for example, and assumes that not all attempts hang. If you need puppet to actually apply when you run the command, then no workaround is available. [Development Fix] Fixed upstream by removing some unnecessary thread-exclusive locks that were evidently causing a deadlock when the facter module is used from puppet in the "puppet apply" case. [Stable Fix] Development fix cherry-picked from upstream. [Test Case] 1. apt-get install -y puppet 2. cat > /etc/puppet/manifests/site.pp <<EOT file { '/tmp/foo': content => 'bar'; } EOT 3. successes=0; failures=0; for i in `seq 1 100`; do timeout -k 35s 30s puppet apply /etc/puppet/manifests/site.pp; rv=$?; echo "Exit status $rv"; if [ $rv -eq 0 ]; then successes=$(($successes+1)); else failures=$(($failures+1)); fi; done; echo "Successses: $successes; failures: $failures" Expected result: Successes: 100; failures: 0 Actual result (approx): Successes: 80; failures: 20 Note that this is dependent on a race condition, so this is difficult to reproduce. I have not managed to reproduce the fault reliably except on particular servers where it happens to occur. I have a server where it is happening, and the fix eliminates the problem, and am prepared to use this for -proposed verification. [Regression Potential] The code that runs inside each lock section is trivial, clearly does not need a lock, and upstream concurs: http://projects.puppetlabs.com/issues/12723 [Original Description] I found a bug with Facter that's affecting the version distributed with 12.04. Upstream bug report here: http://projects.puppetlabs.com/issues/12723 This makes puppet completely unusable for us unless this change is applied. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: facter 1.6.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-virtual 3.2.14 Uname: Linux 3.2.0-23-virtual x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 19:11:56 2012 Ec2AMI: ami-2616cd4f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: c1.medium Ec2Kernel: aki-825ea7eb Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron:  LC_CTYPE=en_US.UTF-8  TERM=xterm  LANG=en_US.UTF-8  SHELL=/usr/bin/zsh SourcePackage: facter UpgradeStatus: No upgrade log present (probably fresh install)
2013-07-02 13:53:45 Jorge Bastida bug added subscriber Jorge Bastida
2013-07-18 07:59:58 Dave Walker facter (Ubuntu Precise): status In Progress Fix Committed
2013-07-18 08:00:01 Dave Walker bug added subscriber Ubuntu Stable Release Updates Team
2013-07-18 08:00:07 Dave Walker bug added subscriber SRU Verification
2013-07-18 08:00:18 Dave Walker tags amd64 apport-bug ec2-images precise amd64 apport-bug ec2-images precise verification-needed
2013-07-28 15:06:29 Robie Basak tags amd64 apport-bug ec2-images precise verification-needed amd64 apport-bug ec2-images precise verification-done
2013-09-19 09:55:49 Launchpad Janitor facter (Ubuntu Precise): status Fix Committed Fix Released
2013-09-19 09:55:54 Colin Watson removed subscriber Ubuntu Stable Release Updates Team