Issue #2162 has been updated by Aurélien Cedeyn.
Hi, Is there any plan to fix this issue ? I am using 0.25.4 and I see that this bug was opened one year ago... puppetd -t --noop is very useful to me to check the configuration status of my servers before applying any changes. It's also important to have a correct return code when the server is not reachable. Thanks Aurelien ---------------------------------------- Bug #2162: Exit code 0 on failed puppetd execution http://projects.puppetlabs.com/issues/2162 Author: Pete Emerson Status: Accepted Priority: Normal Assigned to: Category: Target version: 0.25.6 Affected version: 0.24.7 Keywords: Branch: I intentionally broke my puppet_node_classifier to see what exit code would come out of puppetd: # /usr/sbin/puppetd --server=01.web.test --test err: Could not retrieve catalog: Could not find node '01.web.test'; cannot compile warning: Not using cache on failed catalog # echo $? 0 Shouldn't this be a non-zero exit code? Pete -- 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.
