Issue #1672 has been updated by martin.
Puppet should fail gracefully even if commands it invokes fail. It should not leave the system in a state which you can not recover from. When puppet calls Puppet::Util.execute(["crontab", output_file.path], :uid => @path) it should only remove the output_file when the above call is successful, and alert the admin of the failure and point to the original file for manual recovery. ---------------------------------------- Bug #1672: crontab update craps out in zones on Solaris 10 http://projects.reductivelabs.com/issues/show/1672 Author: martin Status: Needs more information Priority: High Assigned to: Category: Target version: Complexity: Unknown Affected version: 0.24.5 Keywords: I'm using the crontab type to add an entry, and the update craps out with the following error: <pre> debug: Executing 'crontab /tmp/puppet20081021-25388-z3vqav-0' err: Could not apply complete catalog: Could not write crontab for root: No child processes </pre> and the major problem is that it truncates the crontab file. If it fails it should revert it back to the original contents instead of abandoning it in an unknown state or at least give you a pointer to where the original crontab contents can be found. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
