Issue #19883 has been updated by Luke Bigum.

Terrible terrible formatting sorry, I seem to have lost WYSIWYG in your 
RedMine, lets try again:

file { '/tmp/foo':
ensure => present,
tag    => [ 'woof', 'cow' ],
}
service { 'foo':
ensure => running,
tag    => [ 'woof', 'cow' ],
}
file { '/tmp/bar':
ensure => present,
notify => Service['foo'],
}



$ puppet apply test.pp --tags file --noop
Notice: /Stage[main]//File[/tmp/foo]/ensure: current_value absent, should be 
present (noop)
Notice: /Stage[main]//File[/tmp/bar]/ensure: current_value absent, should be 
present (noop)
Notice: /Stage[main]//Service[foo]: Would have triggered 'refresh' from 1 events
Notice: Class[Main]: Would have triggered 'refresh' from 3 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events



$ puppet apply test.pp --noop
Notice: /Stage[main]//File[/tmp/foo]/ensure: current_value absent, should be 
present (noop)
Notice: /Stage[main]//File[/tmp/bar]/ensure: current_value absent, should be 
present (noop)
Notice: /Stage[main]//Service[foo]/ensure: current_value stopped, should be 
running (noop)
Notice: /Stage[main]//Service[foo]: Would have triggered 'refresh' from 1 events
Notice: Class[Main]: Would have triggered 'refresh' from 4 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events
Notice: Finished catalog run in 0.20 seconds

----------------------------------------
Bug #19883: refresh events logged for resources that don't match tags
https://projects.puppetlabs.com/issues/19883#change-87510

* Author: Luke Bigum
* Status: Unreviewed
* Priority: Low
* Assignee: 
* Category: 
* Target version: 
* Affected Puppet version: 3.1.1
* Keywords: 
* Branch: 
----------------------------------------
When using tags to restrict resources that notify other resources, the refresh 
event appears in the logs. See the example below where a File notifies a 
Service:

   file { '/tmp/foo':
     ensure => present,
     tag    => [ 'woof', 'cow' ],
   }
   service { 'foo':
     ensure => running,
     tag    => [ 'woof', 'cow' ],
   }
   file { '/tmp/bar':
     ensure => present,
     notify => Service['foo'],
   }

   $ puppet apply test.pp --tags file --noop
   Notice: /Stage[main]//File[/tmp/foo]/ensure: current_value absent, should be 
present (noop)
   Notice: /Stage[main]//File[/tmp/bar]/ensure: current_value absent, should be 
present (noop)
   Notice: /Stage[main]//Service[foo]: Would have triggered 'refresh' from 1 
events
   Notice: Class[Main]: Would have triggered 'refresh' from 3 events
   Notice: Stage[main]: Would have triggered 'refresh' from 1 events

Service[foo] is not actioned upon because it does not have a matching tag, 
however we still get a log message about it. This could be misinterpreted in to 
thinking that Service[foo] would be restarted.

The log message probably comes from the File resource that "sends" the refresh 
event, up to you whether you think it's worth squashing or not as it would be a 
very slight change in behaviour.


-- 
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.


Reply via email to