Issue #3301 has been updated by Thomas Bellman.
This is the expected behaviour of notice(), warning(), and so on. They are
even documented that way: "Log a message *on the server* at level notice" (my
emphasis).
Functions are evaluated in the puppetmaster, not in the client. You should use
the 'notify' resource type for what you want:
notify { "foo": message => "Uh oh!"; }
(I think you can use the 'loglevel' metaparameter to control if the message
will be logged as a notice, warning, error, and so on.)
Maybe the documentation for those functions could be even more explicit about
this, but their behaviour is correct.
----------------------------------------
Bug #3301: puppetd does not display notice() & co messages on the console when
logdest is set to console
http://projects.reductivelabs.com/issues/3301
Author: Xavier Delaruelle
Status: Needs more information
Priority: Normal
Assigned to:
Category: error reporting
Target version:
Affected version: 0.25.4
Keywords:
Branch:
Hello,
When using some notice/warning/... statements in some class, it appears that
puppetd does not print their relative text on the console even if "--logdest
console" is set. The messages from the notice/warning/... are only put in the
syslog.
I would like to use notice/warning and co to alert the sysadmin running puppetd
that some manual action have to be done when a particular resource is updated.
So having these messages printed on the console when the logdest is set
accordingly could be useful.
Regards,
Xavier
--
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://reductivelabs.com/redmine/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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
