subject:"\[Bug 986973\] Re\: Facter bug causes puppet to hang"

(this appears fixed in Saucy, so just the Precise SRU needed)

** Description changed:

+ [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
+  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)

** Changed in: facter (Ubuntu Precise)
   Status: New = In Progress

** Changed in: facter (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

** Description changed:

  [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
+  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)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

(this appears fixed in Saucy, so just the Precise SRU needed)

** Description changed:

+ [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
+  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)

** Changed in: facter (Ubuntu Precise)
   Status: New = In Progress

** Changed in: facter (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

** Description changed:

  [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
+  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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-28 Thread Robie Basak

I found a machine exhibiting this problem. On Precise (facter
1.6.5-1ubuntu1), I ran the following experiments:

No patch: puppet apply failed 20 out of 100 runs.
Patched both memory.rb and processor.rb: puppet apply failed 0 out of 100
runs.
Patched only memory.rb: puppet apply failed 23 out of 100 runs.
Pathced only processor.rb: puppet apply failed 0 out of 100 runs.

So for me, patching just processor.rb fixed the problem. However, this
being a race, it might be that I just wasn't able to trigger a race
involving memory.rb in my specific circumstances.

The patch I used was
https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c.patch.
I can see that at least on Linux, all the affected areas do is parse
/proc/meminfo and /proc/cpuinfo in a way that I don't see why any thread
exclusive locks would be needed at all. Upstream seemed to agree in
https://github.com/puppetlabs/facter/pull/174 and had no explanation for
why they were put in either. So I think it's safe to backport all of the
patch to Precise. I'll do this next week.

** Changed in: facter (Ubuntu Precise)
Assignee: (unassigned) = Robie Basak (racb)

--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-28 Thread Robie Basak

I found a machine exhibiting this problem. On Precise (facter
1.6.5-1ubuntu1), I ran the following experiments:

So for me, patching just processor.rb fixed the problem. However, this
being a race, it might be that I just wasn't able to trigger a race
involving memory.rb in my specific circumstances.

** Changed in: facter (Ubuntu Precise)
Assignee: (unassigned) = Robie Basak (racb)

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-18 Thread Shane Meyers

Installing the patched version of memory.rb from
https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c
helped reduce the number of puppet hangs that we experience, but we were
still getting hung processes.  Attaching strace to a hung puppet
process showed a constant output of the following lines repeated:

31024 futex(0x7f96be6ed5b0, FUTEX_WAKE_PRIVATE, 1) = 0
31024 futex(0x7f96be6ed584, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 
231453, {1371588406, 113327589}, ) = -1 ETIMEDOUT (Connection timed out)
31024 clock_gettime(CLOCK_REALTIME, {1371588406, 113578908}) = 0
31024 futex(0x7f96be6ed5b0, FUTEX_WAKE_PRIVATE, 1) = 0
31024 futex(0x7f96be6ed584, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 
231455, {1371588406, 123578908}, ) = -1 ETIMEDOUT (Connection timed out)
31024 clock_gettime(CLOCK_REALTIME, {1371588406, 123789011}) = 0

It turns out that puppet isn't actually hung, but is waiting forever for
the futex() call to stop timing out.

Once I copied in the patched processor.rb from the same git changeset
linked above, the hang problem stopped occurring for us.  So from my
perspective, both memory.pp and processor.rb need to be patched in the
puppet 1.6.5 (precise) package.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-18 Thread Jared Biel

@Shane

Yes - it appears you are correct and I was in error in my previous
comment. The source file lib/facter/processor.rb does not make use of
Thread::Exclusive (except for Windows), but lib/facter/util/processor.rb
does, so it's necessary to patch that file also.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-18 Thread Shane Meyers

Installing the patched version of memory.rb from
https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c
helped reduce the number of puppet hangs that we experience, but we were
still getting hung processes.  Attaching strace to a hung puppet
process showed a constant output of the following lines repeated:

31024 futex(0x7f96be6ed5b0, FUTEX_WAKE_PRIVATE, 1) = 0
31024 futex(0x7f96be6ed584, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 
231453, {1371588406, 113327589}, ) = -1 ETIMEDOUT (Connection timed out)
31024 clock_gettime(CLOCK_REALTIME, {1371588406, 113578908}) = 0
31024 futex(0x7f96be6ed5b0, FUTEX_WAKE_PRIVATE, 1) = 0
31024 futex(0x7f96be6ed584, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 
231455, {1371588406, 123578908}, ) = -1 ETIMEDOUT (Connection timed out)
31024 clock_gettime(CLOCK_REALTIME, {1371588406, 123789011}) = 0

It turns out that puppet isn't actually hung, but is waiting forever for
the futex() call to stop timing out.

Once I copied in the patched processor.rb from the same git changeset
linked above, the hang problem stopped occurring for us.  So from my
perspective, both memory.pp and processor.rb need to be patched in the
puppet 1.6.5 (precise) package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-18 Thread Jared Biel

@Shane

Yes - it appears you are correct and I was in error in my previous
comment. The source file lib/facter/processor.rb does not make use of
Thread::Exclusive (except for Windows), but lib/facter/util/processor.rb
does, so it's necessary to patch that file also.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

We'll also need this fixed in Saucy before we can commence an SRU. What
is the fix needed in Saucy? Just memory.rb? The same patch? Or
processor.rb as well?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

@Shane

Could you please confirm the patch that you're using on memory.rb, and
confirm that this fixes the problem for you?

I've also been seeing 'puppet apply' hanging via cron, but never figured
out if this was the issue or if this patch fixed it. I've been working
around it with a timeout.

If we can get some confidence in the fix, I'll put this forward as an
SRU in Precise.

** Changed in: facter (Ubuntu Precise)
 Assignee: Marc Cluet (lynxman) = (unassigned)

** Changed in: facter (Ubuntu Precise)
   Status: Won't Fix = New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

We'll also need this fixed in Saucy before we can commence an SRU. What
is the fix needed in Saucy? Just memory.rb? The same patch? Or
processor.rb as well?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

@Shane

Could you please confirm the patch that you're using on memory.rb, and
confirm that this fixes the problem for you?

I've also been seeing 'puppet apply' hanging via cron, but never figured
out if this was the issue or if this patch fixed it. I've been working
around it with a timeout.

If we can get some confidence in the fix, I'll put this forward as an
SRU in Precise.

** Changed in: facter (Ubuntu Precise)
 Assignee: Marc Cluet (lynxman) = (unassigned)

** Changed in: facter (Ubuntu Precise)
   Status: Won't Fix = New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-12 Thread Shane Meyers

It would be fantastic if we could get memory.rb back ported to Precise,
as this is really irritating to need to maintain a separate copy of
memory.rb.  Without the patched version, we experience many hangs per
day with 'puppet apply' running via cron.  Surprising to see a hang bug
remain for so long with an LTS release.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

2013-06-12 Thread Shane Meyers

It would be fantastic if we could get memory.rb back ported to Precise,
as this is really irritating to need to maintain a separate copy of
memory.rb.  Without the patched version, we experience many hangs per
day with 'puppet apply' running via cron.  Surprising to see a hang bug
remain for so long with an LTS release.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

@Robie Basak

The copy of memory.rb that you linked in your update does contain the
fix (removal of require 'thread' etc.) I just checked out the tag
1.7.0 and found the commit
(https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c).
Note: that commit is only for memory.rb. Patching of processor.rb may
also necessary.

It'd be great if this were backported to the Ubuntu versions because
right now it's necessary for us to maintain our own version with patched
memory.rb and processor.rb. The code is also present in quantal and
raring (facter 1.6.9), although I cannot say if this bug also affects
those distributions.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

I just did some digging and found that processor.rb isn't affected in
versions 1.6.5 (precise) or 1.6.9. So, commit
9ff4453b2f0843df887ae1ec2098a4336291df0c is the only necessary one to
cherry-pick here.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 986973] Re: Facter bug causes puppet to hang

@Robie Basak

The copy of memory.rb that you linked in your update does contain the
fix (removal of require 'thread' etc.) I just checked out the tag
1.7.0 and found the commit
(https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c).
Note: that commit is only for memory.rb. Patching of processor.rb may
also necessary.

It'd be great if this were backported to the Ubuntu versions because
right now it's necessary for us to maintain our own version with patched
memory.rb and processor.rb. The code is also present in quantal and
raring (facter 1.6.9), although I cannot say if this bug also affects
those distributions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973

Title:
  Facter bug causes puppet to hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/986973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 986973] Re: Facter bug causes puppet to hang