Jira (PDB-16) Store status for reports

[Jason Antman (JIRA)]

Title: Message Title

Jason Antman commented on an issue   Re: Store status for reports Wondering if there's an update on this? 1) Yes, the current report format only provides a "status" property (failed, changed, unchanged) that can determine the overall status, but nothing to determine a failure cause. However, PUP-283 and PUP-916 would fix that. Perhaps a spec for this "failure cause" data, to be included in a future Report Format 5, could be developed, implemented on the PDB side, and simply be empty until reports including it come in? 2) I understand that this is a PE customer ticket (I'm a PE customer as well), but there are a lot of us who would like to see this implemented ASAP in the OSS version... Not being able to tell whether a run was an overall failure or not is a serious gap in PuppetDB's usefulness. Add Comment   PuppetDB / PDB-16 Store status for reports We recently learned that when a puppet run fails due to catalog compilation error or catalog timeout, the agent will submit a report with a status of `failed`, but without any events. Because the current implementation of report storage in PuppetDB relies entirely on events to indicate success/failure, there is no way to look at the PuppetDB data and det... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.