Puppet Labs

04/29/2010

05:17 pm Puppet Bug #3350: Could not find a default provider for cron error prevents entire puppetd run

Agreed.

04/08/2010

09:34 pm Puppet Bug #3350: Could not find a default provider for cron error prevents entire puppetd run

puppetd -v --no-daemonize --trace --debug --onetime
debug: Failed to load library 'shadow' for feature 'libshadow'...

03/08/2010

08:02 pm Puppet Bug #3350 (Duplicate): Could not find a default provider for cron error prevents entire puppetd run

While running puppetd on a gentoo box without any cron packages installed, puppetd stops with the following error:
...

12/15/2009

10:11 pm Puppet Bug #2765: puppetrun --no-fqdn configuration option is effectively always set

If you specify --no-fqdn, then the hostname should only be the CN. If the --no-fqdn option is not specified, the hos...

11/05/2009

04:17 am Puppet Bug #2789 (Closed): puppetrun triggered runs that do not specify tags fail to apply configuration...

When puppetd is triggered by puppetrun without --tags on the command line, the @tags@ ruby object is set to @[""]@ wh...

11/02/2009

08:09 pm Puppet Bug #2765: puppetrun --no-fqdn configuration option is effectively always set

Markus Roberts wrote:
> There is a reasonably high risk of introducing regressions here.
Agreed. I believe reins...

10/31/2009

01:04 am Puppet Bug #2765 (Closed): puppetrun --no-fqdn configuration option is effectively always set

puppetrun as of 0.25.1 always uses the cn= value of the dn: as the entire node's hostname.
Earlier versions (I che...