Issue #11367 has been reported by Matt Robinson.
----------------------------------------
Bug #11367: noop runs shouldn't get refresh events triggered on stages and
class main
https://projects.puppetlabs.com/issues/11367
Author: Matt Robinson
Status: Accepted
Priority: Normal
Assignee:
Category:
Target version: 2.7.x
Affected Puppet version: 2.7.9
Keywords:
Branch:
In Puppet 2.7.9 we get notices about Class[Main] and Stage[main] that we
shouldn't when running noop
>puppet apply --noop -e "file { '/tmp/bar' : ensure => present }"
notice: /Stage[main]//File[/tmp/bar]/ensure: current_value absent, should
be present (noop)
notice: /tmp/bar: Would have triggered 'refresh' from 1 events
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.05 seconds
In Puppet 2.6.13 we get better output
> puppet apply --noop -e "file { '/tmp/bar' : ensure => present }"
The interpreter parameter to 'setcode' is deprecated and will be removed in
a future version.
notice: /Stage[main]//File[/tmp/bar]/ensure: current_value absent, should
be present (noop)
notice: Finished catalog run in 0.04 seconds
--
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.
