On Wed, Oct 06, 2010 at 09:18:07AM -0700, Patrick wrote:
>
>
> I didn't quite understand what you said.
Here's an example manifest that demonstrates both problems:
file { '/tmp/shared': ensure => 'directory' }
file { '/tmp/shared/notice': ensure => 'file' }
file { '/tmp/shared/verbose':
ensure => 'file',
loglevel => 'verbose'
}
tidy { '/tmp/shared':
recurse => true,
loglevel => 'verbose'
}
The first issue is about loglevel; at puppet's default logging level,
only the creation of the first two resources should be logged. In fact,
the actions of the first two and the final (tidy) are logged, because
tidy is ignoring loglevel.
The second issue is that puppet is logging actions that do not take
place. The tidy resource should delete all files in /tmp/shared *apart*
from the ones created in the manifest. This is expected behaviour and
this is what it does. It's a handy way of making sure that a directory
tree contains *only* the files you mean to be there. However, the
imaginary deletion of those files is being logged. And because it is
imaginary, and the files remain in place, it's logged on *every* run.
>I hope this general rule helps:
>
> If puppet is logging something about a resource every run AND not
> changing anything AND not failing, I think you should file a bug.
Done.
--
Bruce
Explota!: miles de lemmings no pueden estar equivocados.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
