Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Rob Braden updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Rob Braden Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Nick Walker commented on PUP-8611 Re: Crontab gets erased after error during agent run Based on PUP-2643, I would expect that we'd fail if we can't read the file. In that ticket we chose to implement "2. Fail completely and do not manage the crontab entries if the file is in an invalid state." I'd be in favor of a new cron attribute that controls whether we blow away the file when it can't be read or we decide to fail when it can't be read. However, I'm guessing that'd be a non-trivial thing to add in. Without that I think we should error on the side of safety and fail when crontab can't be read. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Charlie Sharpsteen commented on PUP-8611 Re: Crontab gets erased after error during agent run There's probably some tension here between two competing use cases: Some folks prefer we don't touch a crontab if we can't parse it. Some folks want us to overwrite the crontab if it can't be parsed — so that puppet can fix broken cron entries. Maybe a happy medium in this case is to avoid writing a blank crontab if an error occurred during parsing and no cron resources are targetting that tab? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: Losing crontab because of an error during the run can be hugely disruptive to customers, especially in situations where only some of their cron jobs are managed by puppet and they are now forced to recreate those in some way. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Owen Rodabaugh CS Severity: 4 - Major CS Business Value: 4 - $ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Josh Cooper commented on PUP-8611 Re: Crontab gets erased after error during agent run PUP-3656 ensured that we don't (in general) swallow exceptions raised during a provider's prefetch method, but it doesn't fix the issue for providers that inherit from ParsedFileProvider, see https://github.com/puppetlabs/puppet/blob/5.5.0/lib/puppet/provider/parsedfile.rb#L262-L270. This affects crontab, host, mount, ssh_authorized_key, etc. I don't understand why silently rescuing the exception and proceeding would ever be a good thing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Eric Sorenson commented on PUP-8611 Re: Crontab gets erased after error during agent run Two things - PE2016.4.2 is on an extremely old version of the puppet agent that lacks many bugfixes and needs to be updated. Also, this may be related to https://tickets.puppetlabs.com/browse/PUP-3656 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Craig Gomes Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Craig Gomes Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Change By: Eric Delaney Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title
Patrick Grant updated an issue
Puppet / PUP-8611
Crontab gets erased after error during agent run
Change By:
Patrick Grant
*OS Name/Version: PE Master/Agent Version 2016.4.2 / Master RHEL 6.9 / Agent AIX 7.1*Customer experienced high utilization of paging space on his agent which caused the following error during a puppet run: {code:java} Could not prefetch cron provider 'crontab' target 'root': Could not read crontab for root: Not enough space - fork(2). Treating as empty{code}After the error occurred the customer's crontab was wiped and it left only the following: {code:java} # HEADER: This file was autogenerated at 2017-11-09 13:20:05 -0500 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that the comments starting with 'Puppet Name' should # HEADER: not be deleted, as doing so could cause duplicate cron jobs. {code}Another agent run after the paging problems were fixed did not resolve the crontab and it had to be restored from a backup. After the file was present, subsequent puppet runs now correct the crontab entries. *Desired Behavior:* When the error below occurs, crontab should not be wiped and should be left as is{code:java} Could not prefetch cron provider 'crontab' target 'root': Could not read crontab for root: Not enough space - fork(2). Treating as empty{code}*Actual Behavior:* Crontab gets completely wiped when the error occurs during a puppet run.
Add Comment
This message was sent by Atlassian J
Jira (PUP-8611) Crontab gets erased after error during agent run
Title: Message Title Patrick Grant created an issue Puppet / PUP-8611 Crontab gets erased after error during agent run Issue Type: Bug Assignee: Unassigned Created: 2018/03/28 3:20 AM Priority: Normal Reporter: Patrick Grant OS Name/Version: PE Master/Agent Version 2016.4.2 / Master RHEL 6.9 / Agent AIX 7.1 Customer experienced high utilization of paging space on his agent which caused the following error during a puppet run: Could not prefetch cron provider 'crontab' target 'root': Could not read crontab for root: Not enough space - fork(2). Treating as empty After the error occurred the customer's crontab was wiped and it left only the following: # HEADER: This file was autogenerated at 2017-11-09 13:20:05 -0500 by puppet. # HEADER: While it can still be managed manually, it is definitely not recommended. # HEADER: Note particularly that th
