Jira (PUP-2089) Error messages did not store in last_run_summary.yaml when config failed.

[Sean McDonald (JIRA)]

Sean McDonald assigned an issue to Unassigned

Puppet / PUP-2089 Error messages did not store in last_run_summary.yaml when config failed. Change By: Sean McDonald Assignee: Kylo Ginsberg Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-2089 Error messages did not store in last_run_summary.yaml when config failed.

Change By: Moses Mendoza Labels: puppet-agent  triaged

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-2089 Error messages did not store in last_run_summary.yaml when config failed.

Change By: Moses Mendoza Team: Agent

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-2089 Error messages did not store in last_run_summary.yaml when config failed.

Change By: Moses Mendoza Labels: puppet-agent  triaged

Add Comment

[Anton Fomenko (JIRA)]

Anton Fomenko commented on PUP-2089

Re: Error messages did not store in last_run_summary.yaml when config failed. Any chances of this being fixed.

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-2089

Error messages did not store in last_run_summary.yaml when config failed.

Change By: Josh Cooper Labels: puppet-agent

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-2089

Re: Error messages did not store in last_run_summary.yaml when config failed. Still an issue in 6.4. If we fail to download a catalog due to server complication error, the last run summary doesn't report any errors: --- version: config: puppet: 6.4.0 resources: changed: 0 corrective_change: 0 failed: 0 failed_to_restart: 0 out_of_sync: 0 restarted: 0 scheduled: 0 skipped: 0 total: 0 time: fact_generation: 2.147443000227213 node_retrieval: 0.14986300002783537 plugin_sync: 0.3799709999002516 total: 2.938147 last_run: 1553832920 changes: total: 0 events: failure: 0 success: 0 total: 0

Add Comment

[Damon Maria (Jira)]

Damon Maria commented on PUP-2089

Re: Error messages did not store in last_run_summary.yaml when config failed.

What about adding a "last_retrieve" timestamp (like last_run) into the summary. While the reason would not be known at least we could detect the failure.

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-2089

Re: Error messages did not store in last_run_summary.yaml when config failed.

This should be relatively easy now that PUP-8288 is fixed. Puppet now keeps track of whether the transaction completed successfully (it assumes failure and only sets the transaction_completed variable to true if it gets to the end. Puppet also takes that variable into account when determining whether the overall status is success or failure. It should be easy to update the `last_run_summary` to include the overall status and a timestamp of when the last run occurred.

Add Comment