The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

James Sweeny

  • Registered on: 04/14/2012
  • Last connection: 08/14/2014

Projects

Activity

Reported issues: 62

09/04/2013

10:20 am PuppetDB Bug #22380 (Merged - Pending Release): store-usage and temp-usage options are undocumented
Though the default config.ini specifies the purpose of these options, they are not in the official documentation.

05/17/2013

09:55 am Puppet Documentation Bug #20659 (Rejected): Puppetmaster running through passenger doesn;t read either /etc/puppet/pup...
I spoke with Roberto over email and confirmed that this is neither documentation related nor an actual bug. Updating ...

03/18/2013

11:47 am Puppet Bug #19742: Report processor swallows exceptions
Another note, the failing test specifically checks that this feature doesn't exist. I can't see a good reason for thi...

03/14/2013

03:58 pm Puppet Bug #19742: Report processor swallows exceptions
I don't think it's related. #17883 seems to be a problem with the way the processor is loaded, and this bug is very s...
09:45 pm Puppet Bug #19742 (Needs More Information): Report processor swallows exceptions
The report processor terminus catches errors generated during report processing and only logs them. This is fine for ...

11/07/2012

10:20 am Puppet Bug #17466: Bad error from user type when no provider is available
Also, the relevant stack trace:...
10:18 am Puppet Bug #17466 (Accepted): Bad error from user type when no provider is available
The user type gives "undefined method `exists?' for nil:NilClass" when it can't find a suitable provider. This should...

Also available in: Atom