Issue #19379 has been updated by Matthaus Owens. Status changed from Merged - Pending Release to Closed
Released in Puppet 3.2.0-rc1 ---------------------------------------- Bug #19379: exec: logoutput=>on_error always logs https://projects.puppetlabs.com/issues/19379#change-89603 * Author: Chris Ritson * Status: Closed * Priority: Normal * Assignee: * Category: exec * Target version: 3.2.0 * Affected Puppet version: 3.1.0 * Keywords: logoutput * Branch: https://github.com/puppetlabs/puppet/pull/1524 ---------------------------------------- We are using an exec construct to look for unwanted long-running processes and kill them. This is currently logging everything as "notice" messages. In an attempt to suppress this when it is not needed, I tried to use the logoutput parameter in the exec. The documentation contains the following mutually inconsistent statements:- * Values are true, false, on_failure, and any legal log level * Valid values are true, false, on_failure Trying to use a legal syslog level either symbolically "info", info or 6 always raises a compilation/syntax error from the master at run time. Setting this parameter to "on_failure" or "false" always logs output even when this output states that the command was successful. Our master is on 2.7.14, the specific client I was testing on uses 2.6.16. -- 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.
