[Puppet - Bug #17877] (Unreviewed) facter is crashing: related to ec2 connect 169.254.169.254?

Issue #17877 has been reported by James Patterson. Bug #17877: facter is crashing: related to ec2 connect 169.254.169.254? https://projects.puppetlabs.com/issues/17877 Author: James Patterson Status: Unreviewed Priority: High Assignee: Category: Target

[Puppet - Bug #17877] facter is crashing: related to ec2 connect 169.254.169.254?

Issue #17877 has been updated by James Patterson. Forcing a downgrade to facter-1.6.14-1 is our current workaround. Bug #17877: facter is crashing: related to ec2 connect 169.254.169.254? https://projects.puppetlabs.com/issues/17877#change-77855 Author:

[Puppet - Bug #17877] facter is crashing: related to ec2 connect 169.254.169.254?

Issue #17877 has been updated by James Patterson. Forcing a downgrade to facter-1.6.14-1 is our current workaround. Bug #17877: facter is crashing: related to ec2 connect 169.254.169.254? https://projects.puppetlabs.com/issues/17877#change-77856 Author:

[Puppet - Bug #17879] (Unreviewed) extract cert name properly from subject DN

Issue #17879 has been reported by Yuri Arabadji. Bug #17879: extract cert name properly from subject DN https://projects.puppetlabs.com/issues/17879 Author: Yuri Arabadji Status: Unreviewed Priority: High Assignee: Category: Target version: Affected

[Puppet - Bug #17879] extract cert name properly from subject DN

Issue #17879 has been updated by Yuri Arabadji. patch --- /usr/local/rvm/gems/ruby-1.9.3-p286@puppet30/gems/puppet-3.0.1/lib/puppet/ssl/base.rb.orig 2012-11-30 10:23:24.531533928 -0500 +++ /usr/local/rvm/gems/ruby-1.9.3-p286@puppet30/gems/puppet-3.0.1/lib/puppet/ssl/base.rb

[Puppet - Bug #16971] (Re-opened) Add values to default resources with the plusignment

Issue #16971 has been updated by Julien Vaubourg. Status changed from Closed to Re-opened Assignee changed from Julien Vaubourg to eric sorenson Thanks for your interest. **Henrik:** I tried your solution, but I have the same problem. Package { require =

[Puppet - Bug #17880] (Unreviewed) When master is not a CA

Issue #17880 has been reported by Yuri Arabadji. Bug #17880: When master is not a CA https://projects.puppetlabs.com/issues/17880 Author: Yuri Arabadji Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version:

[Facter - Bug #17877] facter is crashing: related to ec2 connect 169.254.169.254?

Issue #17877 has been updated by Josh Cooper. Project changed from Puppet to Facter Bug #17877: facter is crashing: related to ec2 connect 169.254.169.254? https://projects.puppetlabs.com/issues/17877#change-77866 Author: James Patterson Status:

[Facter - Bug #17877] (Duplicate) facter is crashing: related to ec2 connect 169.254.169.254?

Issue #17877 has been updated by Josh Cooper. Status changed from Unreviewed to Duplicate Bug #17877: facter is crashing: related to ec2 connect 169.254.169.254? https://projects.puppetlabs.com/issues/17877#change-77867 Author: James Patterson Status:

[Puppet - Bug #17692] Puppet doesn't report environment as fact

Issue #17692 has been updated by Andrew Parker. Assignee changed from Andrew Parker to Henrik Lindberg Bug #17692: Puppet doesn't report environment as fact https://projects.puppetlabs.com/issues/17692#change-77868 Author: Kamil Swiatkowski Status:

[Puppet - Bug #17883] (Unreviewed) Custom reports not working (Class is already defined in Puppet::Reports)

Issue #17883 has been reported by Scott Smith. Bug #17883: Custom reports not working (Class is already defined in Puppet::Reports) https://projects.puppetlabs.com/issues/17883 Author: Scott Smith Status: Unreviewed Priority: Normal Assignee: Category:

[Puppet - Bug #17883] Custom reports not working (Class is already defined in Puppet::Reports)

Issue #17883 has been updated by Ashley Penney. My error is: Error: Could not send report: Error 400 on SERVER: Could not autoload puppet/reports/datadog_reports: Class Datadog_reports is already defined in Puppet::Reports On Puppet 3.0.1. Bug

[Facter - Bug #17855] (Merged - Pending Release) facter fails with in `open': execution expired (Timeout::Error) when using ruby 1.8.7

Issue #17855 has been updated by Andrew Parker. Status changed from In Topic Branch Pending Review to Merged - Pending Release Merged in commit c54f7df Bug #17855: facter fails with in `open': execution expired (Timeout::Error) when using ruby 1.8.7

[Puppet - Bug #7580] (Tests Insufficient) puppet always try to change user's gid on LDAP with same value.

Issue #7580 has been updated by Jeff McCune. Status changed from Accepted to Tests Insufficient Target version set to 3.x Branch set to https://github.com/puppetlabs/puppet/pull/1291 Trevor Hemsley wrote: I have submitted a git pull request for this here

[Puppet - Bug #17883] (Investigating) Custom reports not working (Class is already defined in Puppet::Reports)

Issue #17883 has been updated by eric sorenson. Status changed from Unreviewed to Investigating Assignee set to eric sorenson I am having trouble reproducing this locally -- it's working under 2.7.20 and 3.0.2 w/ the boundary report processor. I noticed a comment on the README.md for

[Puppet - Bug #17287] CentOS client ensuring package every run when set to purge not absent

Issue #17287 has been updated by Greg Swift. Assignee changed from Greg Swift to eric sorenson I'm working off the concept that when I run puppet and there is nothing to do I should see *zero* notices like this. If there is a notice it means that something is being triggered, which means the

[Facter - Refactor #17710] (Accepted) issues with IP facts

Issue #17710 has been updated by Jeff McCune. Status changed from Unreviewed to Accepted Assignee deleted (Jeff McCune) Target version set to 2.x Alex Harvey wrote: Disclaimer - more experienced developers on the project may completely disagree with any or all of this. But for what it's

[Facter - Bug #17794] (Tests Insufficient) zpool_version and zfs_version should not be restricted to only sun and bsd

Issue #17794 has been updated by Jeff McCune. Status changed from In Topic Branch Pending Review to Tests Insufficient Assignee set to Marc Fournier # Failing tests Marc, Thanks, I notice the change is causing tests to fail though. I've updated the pull request discussion [1] with clear

[Puppet - Bug #16112] augeas command 'clearm' returns 'Unknown command'

Issue #16112 has been updated by Jeff McCune. Target version changed from 3.0.x to 3.1.0 Bug #16112: augeas command 'clearm' returns 'Unknown command' https://projects.puppetlabs.com/issues/16112#change-77896 Author: Jacob McCann Status: Merged -

[Puppet - Bug #17883] Custom reports not working (Class is already defined in Puppet::Reports)

Issue #17883 has been updated by eric sorenson. This seems to be a common error when using custom reports: https://github.com/jamtur01/bunraku/issues/1 https://github.com/jamtur01/puppet-hipchat/issues/2 https://github.com/jamtur01/puppet-pushover/issues/1

[Puppet - Bug #17883] Custom reports not working (Class is already defined in Puppet::Reports)

Issue #17883 has been updated by Michael Hobbs. from master with trace=true: /usr/lib/ruby/1.8/puppet/util/autoload.rb:85:in `load'#012/usr/lib/ruby/1.8/puppet/util/autoload.rb:73:in `each'#012/usr/lib/ruby/1.8/puppet/util/autoload.rb:73:in

[Puppet - Bug #16753] (In Topic Branch Pending Review) Need the ability to list all nodes

Issue #16753 has been updated by Henrik Lindberg. Status changed from Accepted to In Topic Branch Pending Review Branch set to https://github.com/puppetlabs/puppet/pull/1305 An implementation of Daniel Pittman's idea is now in https://github.com/puppetlabs/puppet/pull/1305 By default, the

[Puppet - Bug #17230] (Closed) Chaining resource collections is unnecessarily slow

Issue #17230 has been updated by Andrew Parker. Status changed from Needs Decision to Closed As Eric says, I don't see a point in the near future where we'll try to tackle this. I find it more likely we'll tackle this by fixing up the algorithm we use for applying catalogs. The proposed

[Puppet - Bug #17883] Custom reports not working (Class is already defined in Puppet::Reports)

Issue #17883 has been updated by eric sorenson. I see what's going on.. that error message is a real problem in the report processor, which needs a patch to fix. The first time through, you see the real error, but subsequent attempts show the 'already defined' error. pre Debug: Received

[Puppet - Bug #4537] nagios_* resources interact wrongly with purge-directories

Issue #4537 has been updated by Joshua Hoblitt. I just encountered this today with my 2.7.19 master. The nagios_* types really should behave as if they are a file type. Bug #4537: nagios_* resources interact wrongly with purge-directories

[Puppet - Bug #3299] owner of files created by nagios resource types

Issue #3299 has been updated by Joshua Hoblitt. I feel that all of the nagios_* types should allow owner, group, mode similar to the file type. Bug #3299: owner of files created by nagios resource types

[Facter - Bug #17794] (In Topic Branch Pending Review) zpool_version and zfs_version should not be restricted to only sun and bsd

Issue #17794 has been updated by Marc Fournier. Status changed from Tests Insufficient to In Topic Branch Pending Review Jeff, I don't seem to be able to re-open the pull-request you closed on github. So I opened another one: https://github.com/puppetlabs/facter/pull/366 Also, I don't have

[Puppet - Feature #17190] detailed accounting/debugging of catalog compilation times

Issue #17190 has been updated by Joshua Hoblitt. Hmm - thinking about it some more, I don't think the profiling process necessarily needs to be bound to the master. Something like this would be really useful: puppet catalog compile --trace ... Re: Master side, what about allowing the

[Puppet - Bug #12833] Password property for User type is broke in OS X 10.8

Issue #12833 has been updated by Gary Larizza. Branch changed from https://github.com/puppetlabs/puppet/pull/1266 to https://github.com/puppetlabs/puppet/pull/1306 Clay found an edge-case wherein a 10.6-style user that existed on a 10.8 machine, who had NEVER logged into the machine after it

[Puppet - Feature #17190] detailed accounting/debugging of catalog compilation times

Issue #17190 has been updated by eric sorenson. Hmm... I wonder if some of this is already available in performance instrumentation framework that Brice added in #9584. Feature #17190: detailed accounting/debugging of catalog compilation times

[Puppet - Bug #17887] (Unreviewed) Mocha expectation failure during property sync results in Puppet::Util::Log requires a message

Issue #17887 has been reported by Dominic Cleal. Bug #17887: Mocha expectation failure during property sync results in Puppet::Util::Log requires a message https://projects.puppetlabs.com/issues/17887 Author: Dominic Cleal Status: Unreviewed Priority:

[Puppet - Bug #17887] (In Topic Branch Pending Review) Mocha expectation failure during property sync results in Puppet::Util::Log requires a message

Issue #17887 has been updated by Dominic Cleal. Status changed from Unreviewed to In Topic Branch Pending Review Target version set to 3.0.x Branch set to https://github.com/puppetlabs/puppet/pull/1307 Bug #17887: Mocha expectation failure during

[Facter - Bug #17890] (Accepted) Unable to add resolve for zones: private method `split' called for nil:NilClass

Issue #17890 has been reported by Josh Cooper. Bug #17890: Unable to add resolve for zones: private method `split' called for nil:NilClass https://projects.puppetlabs.com/issues/17890 Author: Josh Cooper Status: Accepted Priority: Normal Assignee:

[Puppet - Bug #17692] (Duplicate) Puppet doesn't report environment as fact

Issue #17692 has been updated by Henrik Lindberg. Status changed from Accepted to Duplicate This is basically a duplicate of issue #16753 which now has a solution in review (making it possible to query). Bug #17692: Puppet doesn't report environment as

[Facter - Bug #17840] Processor CPU enumeration fails for x86 Windows/Gentoo systems

Issue #17840 has been updated by Matthaus Owens. Target version changed from 1.6.16 to 1.6.17 Bug #17840: Processor CPU enumeration fails for x86 Windows/Gentoo systems https://projects.puppetlabs.com/issues/17840#change-77911 Author: Adrien Thebo

[Facter - Bug #17487] errors related to IP facts sometimes printed on HP-UX platforms

Issue #17487 has been updated by Matthaus Owens. Target version changed from 1.6.16 to 1.6.17 Bug #17487: errors related to IP facts sometimes printed on HP-UX platforms https://projects.puppetlabs.com/issues/17487#change-77912 Author: Alex Harvey

[Facter - Bug #17855] (Closed) facter fails with in `open': execution expired (Timeout::Error) when using ruby 1.8.7

Issue #17855 has been updated by Matthaus Owens. Status changed from Merged - Pending Release to Closed Released in Facter 1.6.16 Bug #17855: facter fails with in `open': execution expired (Timeout::Error) when using ruby 1.8.7

[Puppet] 'Downloading Puppet' wiki page has been updated

The 'Downloading Puppet' wiki page has been updated by Matthaus Owens. Downloading Puppet: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet View differences: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet/diff/223 -- You have received this

[Facter] 'Wiki' wiki page has been updated

The 'Wiki' wiki page has been updated by Matthaus Owens. Wiki: https://projects.puppetlabs.com/projects/facter/wiki/Wiki View differences: https://projects.puppetlabs.com/projects/facter/wiki/Wiki/diff/56 -- You have received this notification because you have either subscribed to it, or are