Issue #14853 has been updated by konrad rzentarzewski.
ok, i think that i misunderstood how loglevel works. i think that i have
different problem: loglevel sets actual level at which messages are emitted,
ie.:
[in syslog at WARNING level]
Mar 14 17:36:37 devel1 puppet-agent[25028]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/ensure) defined content as
'{md5}acbd18db4cc2f85cedef654fccc4a4d8'
for:
node devel1 {
file { "/tmp/test123":
content => "foo",
loglevel => warning,
}
}
but there is lacking an option to supress logging for given resource (say that
/tmp/test123 contains sensitive information), ie:
[in syslog at NOTICE level]
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content)
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) ---
/tmp/test123#0112013-03-14 17:36:37.000000000 +0100
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) +++
/tmp/puppet-file20130314-1514-bdsn7k-0#0112013-03-14 17:46:40.000000000 +0100
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) @@ -1 +1 @@
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) -foo
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) \ No newline at end of
file
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) +bar
Mar 14 17:46:40 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) \ No newline at end of
file
[in syslog at INFO level]
Mar 14 17:46:41 devel1 puppet-agent[1514]: FileBucket adding
{md5}acbd18db4cc2f85cedef654fccc4a4d8
Mar 14 17:46:41 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]) Filebucketed /tmp/test123 to
puppet with sum acbd18db4cc2f85cedef654fccc4a4d8
[in syslog at WARNING level]
Mar 14 17:46:41 devel1 puppet-agent[1514]:
(/Stage[main]//Node[devel1]/File[/tmp/test123]/content) content changed
'{md5}acbd18db4cc2f85cedef654fccc4a4d8' to
'{md5}37b51d194a7513e45b56f6524f2d51f2'
for:
node devel1 {
file { "/tmp/test123":
content => "bar",
loglevel => warning,
}
}
this is inconsistent: resource is logged in 3 levels: info, notice and warning.
if it would only log at level specified by loglevel i'd set it to "DEBUG" and
drop logging at this level in rsyslog, ie:
if (\
($syslogseverity-text == 'debug')\
and ($programname == 'puppet-agent')\
then /dev/null
& ~
testing with 3.1.1 on both sides (agent and master).
am i missing something?
----------------------------------------
Bug #14853: file resource ignores loglevel parameter
https://projects.puppetlabs.com/issues/14853#change-87052
Author: Jo Rhett
Status: Accepted
Priority: Normal
Assignee:
Category: logging
Target version:
Affected Puppet version: 2.7.14
Keywords:
Branch:
I'm trying to make it so that tagmail doesn't return results for syncing files
from our home directories around. Nobody cares ;-)
<pre>
file { '/home/jorhett':
ensure => directory,
owner => 'jorhett',
group => 'jorhett',
recurse => remote,
purge => false,
force => false,
loglevel => debug,
source => 'puppet:///files/home/jorhett',
}
</pre>
However when I run it, loglevel is ignored and it appears as notice in both the
output and the mail message.
<pre>
notice: /File[/home/jorhett/.bash_profile]/content:
--- /home/jorhett/.bash_profile 2012-06-06 17:59:26.059342567 +0000
+++ /tmp/puppet-file20120606-20121-1rfltx2-0 2012-06-06 18:06:58.353336254
+0000
@@ -2,3 +2,4 @@
source ~/.bashrc
fi
export EDITOR="vim"
+export PS1='[\u@\h \W]\$ '
</pre>
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.