Issue #6351 has been updated by James Turnbull.

Testing puppet-bugs list.

Bug #6351: LDAP Nodes documentation is poor

• Author: James Turnbull
• Status: Accepted
• Priority: Normal
• Assignee:
• Category:
• Target version:
• Keywords:
• Branch:
• Affected URL:

http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #6503 has been updated by R.I. Pienaar.

• Status changed from Accepted to Closed

3438231 (1 files in 1 dirs): http://bit.ly/e1a3A7

Feature #6503: Update EC2 demo documentation to reflect new CloudFormation demo

• Author: R.I. Pienaar
• Status: Closed
• Priority: Normal
• Assignee: R.I. Pienaar
• Category: Documentation
• Target version:
• Keywords:
• Branch:
• Affected mCollective version:

Update the docs and screencast to reflect using the new CloudFormation based demo

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #2636 has been updated by James Turnbull.

• Status changed from Accepted to Needs design decision
• Assignee set to Nigel Kersten

Feature #2636: Improvement to module organization

• Author: R.I. Pienaar
• Status: Needs design decision
• Priority: Normal
• Assignee: Nigel Kersten
• Category: modules
• Target version: Statler
• Affected Puppet version: 0.25.0
• Keywords:
• Branch:

hello,

In the case where someone wants to create classes like this:

apache apache::php apache::php::gd apache::php::mysql etc

it would be nice if all php related classes was in one sub directory, currently that isn’t possible without the help of import, it would be great if the above classes could be laid out like this in addition to the current behaviour:

apache/manifests/php/init.pp <– apache::php apache/manifests/php/gd.pp <– apache::php::gd

at present we would need to have apache/manifests/php.pp apache::php class in a different directory than the rest of the php stuff.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #2636 has been updated by Daniel Pittman.

The key difference here is the ability to use module/manifests/foo/init.pp where the current code only supports `module/manifests/foo.pp'. The basic idea, including avoiding import through the autoloader, already works.

Feature #2636: Improvement to module organization

• Author: R.I. Pienaar
• Status: Needs design decision
• Priority: Normal
• Assignee: Nigel Kersten
• Category: modules
• Target version: Statler
• Affected Puppet version: 0.25.0
• Keywords:
• Branch:

hello,

In the case where someone wants to create classes like this:

apache apache::php apache::php::gd apache::php::mysql etc

it would be nice if all php related classes was in one sub directory, currently that isn’t possible without the help of import, it would be great if the above classes could be laid out like this in addition to the current behaviour:

apache/manifests/php/init.pp <– apache::php apache/manifests/php/gd.pp <– apache::php::gd

at present we would need to have apache/manifests/php.pp apache::php class in a different directory than the rest of the php stuff.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #2521 has been updated by James Turnbull.

Kjetil Torgrim Homme wrote:

I don’t think it would hurt anything to call utimes(2) after rename(2), but as far as I can see, it would not solve the problem with cron.

Doesn’t utime just change atime and mtime? It doesn’t change ctime right?

Bug #2521: file{} should update all timestamps when renaming files from temp file.

• Author: R.I. Pienaar
• Status: Accepted
• Priority: Normal
• Assignee:
• Category: file
• Target version:
• Affected Puppet version: 0.24.8
• Keywords:
• Branch:

At present puppet writes new files made with the file resource type using a temp file then renames the temp file. Ruby rename only updates change time not mtime.

This is a problem when interacting with daemons that monitor directories for new files, like /etc/cron.d:

1) puppet creates /etc/cron.d/foo.zxxx 2) crond checks for new files matching its rules, the temp file does not match does not get noticed, crond saves last checked timestamp 3) puppet renames /etc/cron.d/foo.zxxx –> /etc/cron.d/foo and only ctime gets updated not mtime 4) crond checks for new files since last check, finds none.

I think puppet should probably touch both mtime and ctime after renaming a file.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #5905 has been updated by James Turnbull.

• Assignee set to Nigel Kersten

Bug #5905: FileBucket MD5 identifiers should be case insensitive

• Author: Daniel Pittman
• Status: Needs design decision
• Priority: Normal
• Assignee: Nigel Kersten
• Category: API
• Target version:
• Affected Puppet version: development
• Keywords: api, filebucket, dashboard
• Branch:

When referring to various REST API interfaces the Filebucket (and dashboard) require that the hex MD5 is specified matching l[a-f0-9]?/, which mandates lower-case.

Likewise, the input is mapped to the file system without case folding or anything, so depends on puppet coincidentally always generating a lower-case MD5 hash.

If these are strictly internal details that is fine, but so far as I can see we are starting to push features and API details like the REST service that make these increasingly public.

Given that, it would make sense to ensure that we case-fold the MD5 hex input since it is genuinely representation – and that saves every single user everywhere in the world having to remember to do that before every interaction with Puppet.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #5906 has been updated by James Turnbull.

• Assignee set to Nigel Kersten

Bug #5906: puppet master errors have poor formatting

• Author: Mitchell Hashimoto
• Status: Needs design decision
• Priority: Normal
• Assignee: Nigel Kersten
• Category: server
• Target version:
• Affected Puppet version: 2.6.4
• Keywords:
• Branch:

I realize that puppet master needed to be started with root, but ran it as a normal user to see what the output would be like, and it turns out the output is quite garbled!

vagrant <at> vagrantup:~$ puppet master Could not prepare for execution: Got 6 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /var/lib/puppet/bucket; change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /var/lib/puppet/reports; change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /var/lib/puppet/yaml; change from 755 to 750 failed: failed to chmod /var/lib/puppet/log: Operation not permitted - /var/lib/puppet/log; change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /var/lib/puppet/server_data; change from absent to directory failed: Could not set 'directory on ensure: Permission denied - /etc/puppet/manifests

This should ideally be separated out into a more human readable format.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #6493 has been updated by James Turnbull.

• Assignee set to Nigel Kersten

Refactor #6493: The module tool should be part of the regular cli

• Author: Markus Roberts
• Status: Needs design decision
• Priority: Normal
• Assignee: Nigel Kersten
• Category:
• Target version:
• Affected Puppet version:
• Keywords:
• Branch:

Having the puppet module tool (pmt) as a completely separate project hinders its adoption, confuses users, and ghettoizes it.

Making it part of the normal puppet install would resolve much of this.

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.

Issue #6335 has been updated by James Turnbull.

• Assignee set to Nigel Kersten

Bug #6335: Parameterized Class and Defined Resource Type should allow trailing comma in argument list

• Author: Nan Liu
• Status: Needs design decision
• Priority: Normal
• Assignee: Nigel Kersten
• Category:
• Target version:
• Affected Puppet version:
• Keywords:
• Branch:

Parameterized Class and Defined Resource Type does not allow trailing comma. Instead, I would like it to behave like resource attributes where the last comma is optional.

class foo ( $bar, $baz, ) { ... }

You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.