Issue #9167 has been updated by Jo Rhett.
So I must have forgotten to update this ticket. I figured out the cause/effect. If a file is updated but the loglevel is set at debug, it causes this message to appear even though the original message didn't qualify to go out to the recipient. In particular, if you enable mcollective yamlfacts as documented, you'll get this message for all hosts. http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML ---------------------------------------- Bug #9167: tagmail report sends email when nothing happens https://projects.puppetlabs.com/issues/9167#change-81019 Author: Spencer Rinehart Status: Re-opened Priority: Low Assignee: Kelsey Hightower Category: reports Target version: 2.7.19 Affected Puppet version: 2.6.9 Keywords: tagmail Branch: https://github.com/puppetlabs/puppet/pull/618 Since upgrading to the 2.7 series (2.6.8 -> 2.7.3), the tagmail report will send an email with 1 line, shown below, after every run. Before the upgrade, it would only send emails when something occurred during the puppet run. Steps to reproduce: Enable tagmail report Execute a puppet run that produces no updates Expected result: No email sent Actual result: Email sent with line below Email body: Tue Aug 23 13:11:59 -0400 2011 Puppet (notice): Finished catalog run in 16.60 seconds tagmail.conf: all: [email protected] -- 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 [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.
