Issue #7763 has been reported by Dan Bode.
----------------------------------------
Bug #7763: Spurrious logs of 'would have triggered refresh' on noop
https://projects.puppetlabs.com/issues/7763
Author: Dan Bode
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
this is a regression in 2.7.0.
Puppet spuriously logs some refresh notifications when running as noop
Given the manifest:
<pre>
notify { 'fo' : }
</pre>
<pre>
puppet apply --noop /private/tmp/blah.pp
Warning:/opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:
importenv is deprecated after Ruby 1.8.1 (no replacement)
notice: /Stage[main]//Notify[fo]/message: current_value absent, should be fo
(noop)
notice: Class[Main]: Would have triggered 'refresh' from 1 events
notice: Stage[main]: Would have triggered 'refresh' from 1 events
notice: Finished catalog run in 0.03 seconds
</pre>
The logs do no appear when not running as noop
<pre>
notice: fo
notice: /Stage[main]//Notify[fo]/message: defined 'message' as 'fo'
notice: Finished catalog run in 0.05 seconds
</pre>
The messages do not exist on 2.6.8
<pre>
puppet apply --noop /private/tmp/blah.pp
notice: /Stage[main]//Notify[fo]/message: current_value absent, should be fo
(noop)
notice: Finished catalog run in 0.02 seconds
</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 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.
