Jira (PUP-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails

[Moses Mendoza (JIRA)]

Title: Message Title

Moses Mendoza created an issue   Puppet / PUP-6708 Agent does not save local copy of last_run_report.yaml if submission to report server fails Issue Type: Bug Affects Versions: PUP 4.6.2 Assignee: Unassigned Created: 2016/09/15 2:40 PM Priority: Normal Reporter: Moses Mendoza On an Ubuntu 16.04 VM running Puppet 1.6.2 agent: The agent does not appear to save a run report if it fails to submit the report to its report server. root@ubuntu16:~# puppet agent -t --server=foo:1 --report_server=bar:2 --http_connect_timeout=3s --http_debug opening connection to foo:1:8140... Warning: Unable to fetch my node definition, but the agent run will continue: Warning: execution expired Info: Retrieving pluginfacts opening connection to foo:1:8140... Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': execution expired opening connection to foo:1:8140... Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: execution expired Info: Retrieving plugin opening connection to foo:1:8140... Error: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': execution expired opening connection to foo:1:8140... Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: execution expired Info: Loading facts opening connection to foo:1:8140... Error: Could not retrieve catalog from remote server: execution expired Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run opening connection to bar:2:8140... Error: Could not send report: execution expired Afterward, no report is saved on the agent: oot@ubuntu16:~# puppet config print reportdir /opt/puppetlabs/puppet/cache/reports root@ubuntu16:~# ls /opt/puppetlabs/puppet/cache/ clientbucket client_data client_yaml facts.d lib preview state root@ubuntu16:~# ls /opt/puppetlabs/puppet/cache/state/ classes.txt graphs last_run_summary.yaml resources.txt state.yaml transactionstore.yaml root@ubuntu16:~# find /opt/puppetlabs/ -name "last_run_*" /opt/puppetlabs/puppet/cache/state/last_run_summary.yaml root@ubuntu16:~# We do, however, appear to still save last_run_summary.yaml. The contents of it after this run were: root@ubuntu16:~# cat /opt/puppetlabs/puppet/cache/state/last_run_summary.yaml --- version: config: puppet: 4.6.2 time: last_run: 1473975435 root@ubuntu16:~# 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.