Issue #6322 has been updated by Jeremy Pruitt.
I am experiencing the same problem with 2.7.5 (both client and master). If I have a pending change in a noop run, the exit code is 0. If I understand this issue and its resolution, puppet should return a 2 in this case, right? Is anyone else experiencing this with 2.7.5? ---------------------------------------- Bug #6322: --detailed-exitcodes isn't effective when using --noop argument https://projects.puppetlabs.com/issues/6322 Author: Johan Huysmans Status: Closed Priority: Normal Assignee: Matt Robinson Category: executables Target version: 2.6.7 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.
