Bug #11367
noop runs shouldn't get refresh events triggered on stages and class main
| Status: | Accepted | Start date: | 12/13/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 2.7.x | |||
| Affected Puppet version: | 2.7.9 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
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