Issue #6322 has been updated by Ken Barber.
Status changed from Closed to Re-opened
Target version deleted (2.6.7)
I can replicate it on versions 2.6.0, 2.6.9, 2.7.0, 2.7.2, 2.7.5:
$ ~/Development/puppet/bin/puppet apply --noop --detailed-exitcodes noop.pp
; echo $?
notice: /Stage[main]//File[/tmp/os]/ensure: current_value absent, should be
file (noop)
notice: Finished catalog run in 1.08 seconds
0
Whats weird is that even checking out the exact merge entry that was supposed
to fix it I see it not returning an exit code:
$ push ~/Development/puppet; git checkout
1172a4ee50040843e0e4b5eef73183aaf50be855; popd
$ ~/Development/puppet/bin/puppet apply --noop --detailed-exitcodes noop.pp
; echo $?
notice: /Stage[main]//File[/tmp/os]/ensure: current_value absent, should be
file (noop)
notice: Finished catalog run in 1.08 seconds
0
I hope I'm wrong but this _may_ have never worked as intended.
----------------------------------------
Bug #6322: --detailed-exitcodes isn't effective when using --noop argument
https://projects.puppetlabs.com/issues/6322
Author: Johan Huysmans
Status: Re-opened
Priority: Normal
Assignee: Matt Robinson
Category: executables
Target version:
Affected Puppet version: 2.6.2
Keywords:
Branch:
puppetd --server CO_NMS-1 --test --detailed-exitcodes
Has exit code 2 when something is changed.
puppetd --server CO_NMS-1 --test --detailed-exitcodes --noop
Has exit code 0, even when it shows that something would be changed if not
running with noop.
I would expect an exit code 2.
--
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.
