Issue #6961 has been updated by Konrad Scherer.
I am using puppet 2.6.7. I think the confusion over puppet return codes is my fault. I filed a bug about 2 months ago mentioning the puppet error code issue, but I did not properly specify what the exact error code conditions were. I think checking for return code 1 is backwards compatible because the return code 2 was only introduced in puppet 2.6. That should be fairly easy to verify. #4439 looks very promising. Thanks for letting me know about that. Thanks also for the info about Logger and max file size. I never looked into the code deep enough to notice. ---------------------------------------- Bug #6961: mcollective-server-provisioner not using proper puppet return codes https://projects.puppetlabs.com/issues/6961 Author: Konrad Scherer Status: Unreviewed Priority: Normal Assignee: R.I. Pienaar Category: Target version: Keywords: server-provisioner Branch: Affected mCollective version: The exit codes for puppet are: * 0 - Success, not changed * 1 - Error * 2 - Success, files updated I have also made some small additions * Use fqdn of hostname to do lookup * Add init script for debian * Add logrotate config Changes available here: https://github.com/kscherer/mcollective-server-provisioner Branch: wrs -- 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.
