Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Josh Cooper commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero This is a duplicate of PUP-2089. If there is a compilation error, then the last_run_summary.yaml does not reflect that an error occurred, since from the agent's perspective there were no errors applying the catalog (since it never got one). 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Anton Fomenko commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Contents of file os being changed as well as file timestamp ofc. Before # cat /opt/puppetlabs/puppet/cache/state/last_run_summary.yaml --- version: config: puppet: 5.5.6 resources: changed: 0 corrective_change: 0 failed: 0 failed_to_restart: 0 out_of_sync: 0 restarted: 0 scheduled: 0 skipped: 0
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Jacob Helwig commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Anton Fomenko is the last_run timestamp getting updated in your case? I'd expect that the last_run_summary.yaml content you're seeing is from before the server started returning 500 errors on catalog retrieval, so that timestamp is probably much older. The "Error: Could not retrieve catalog; skipping run" message from the agent output shows that it's bailing out before the last_run_summary.yaml would have been written/updated. 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Anton Fomenko commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero I have similar issue: after unsuccessful puppet run there is no data on errors in last_run_summary.yaml # puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Method call, Class[myclass]: expects a value for parameter 'param' (file: /etc/puppetlabs/code/environments/production/modules/mod/manifests/import.pp, line: 11, column: 73) on node mynode Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run [root@mynode ~]# cat /opt/puppetlabs/puppet/cache/state/last_run_summary.yaml --- version:
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Jacob Helwig Assignee: Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Jacob Helwig commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Konrad Scherer, I'm not able to reproduce this on the latest version of Puppet. If I have a duplicate resource in a manifest, I get a last_run_summary.yaml with the following content from an agent run: --- version: config: puppet: 5.4.0 time: last_run: 1518635813 If I run "puppet apply" with a manifest that has duplicate resources, the last_run_summary.yaml doesn't get updated at all. Is this still an issue for you? Add Comment
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Maggie Dreyer commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Jacob Helwig would you mind looking into if this still applies? I think there is an epic around improving failure reporting in Puppet somewhere that this might fit into. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Maggie Dreyer Labels: needs_repo needs_repro Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Justin Stoller Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Moses Mendoza Labels: needs_repo triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Sean McDonald updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Sean McDonald Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Sean McDonald updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Sean McDonald Labels: needs_repo triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Christopher Price updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Christopher Price Component/s: Puppet Server Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Konrad Scherer created an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Components: Puppet Server Created: 28/Oct/14 8:22 AM Priority: Normal Reporter: Konrad Scherer I use the nagios check_puppet.rb script to detect puppet run failures. https://github.com/ripienaar/monitoring-scripts/blob/master/puppet/check_puppet.rb I recently introduced a duplicate resource in my manifests for a few of my machines, but the script did not detect that the puppet run had failed. My other check for the age of the last_run_summary.yaml file did not trigger because puppet agent was updating this file. The last_run_summary looks like this: — resources: scheduled: 0 changed: 0 failed: 0 skipped: 0 total: 357 restarted: 0 out_of_sync: 0 failed_to_restart: 0 events: failure: 0 total: 0 success: 0 changes: total: 0 time: sysctl: 0.001234 service: 1.877718 anchor: 0.00448 ssh_authorized_key: 0.009279 group: 0.001692 config_retrieval: 0.870559930801392 last_run: 1414505487 filebucket: 0.00015 cron: 0.004659 schedule: 0.000962 file: 5.429886 host: 0.000658 exec: 2.216259 total: 11.4154379308014 package: 0.660641 user: 0.33
