Jira (PUP-283) Improve agent error reporting
Title: Message Title Eric Sorenson commented on PUP-283 Re: Improve agent error reporting Thanks E Salberg - I'll take that as authoritative and close this out. 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-283) Improve agent error reporting
Title: Message Title E Salberg commented on PUP-283 Re: Improve agent error reporting It looks like new reporting options cover what we need - I just verified that the classification issue shows up as "intended catalog failure" (the node run still reports a green checkmark despite throwing an error, but I can live with that). We also can pull the cached catalog results from PuppetDB, so I think we're all set. I have seen the dependency report issue recently, so I'll sign on as a watcher to that ticket. 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-283) Improve agent error reporting
Title: Message Title Eric Sorenson commented on PUP-283 Re: Improve agent error reporting (eric0 on a triage run here) I think most of this is fixed now. I know at least catalog retrieval failures now generate a report, and running cached catalog due to new catalog retrieval failure is also flagged. I believe the biggest remaining gap is the thing described in PUP-3042 (dependency cycles produce an agent-side error but no report) - Can one of the watchers (E Salberg, Jason Antman?) confirm? I'd like to close this epic since it got a bit overloaded and focus prioritization on specific remaining problems. 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-283) Improve agent error reporting
Title: Message Title E Salberg commented on PUP-283 Re: Improve agent error reporting Updating here even though this may need its own ticket (I already opened a case with Support): We're also seeing the same behavior (green checkmark / no alerts in the Console or Tagmail) in cases of Classifier conflicts (e.g. one node pinned to two different node groups that set the same variables to different values - myvariable=yes and myvariable=no). The node is not using a cached catalog and the run continues, so the node doesn't even enter Unresponsive state - conflicts could just be there forever. The only indications are on the Node page and a 400 error in the Puppet run log (which doesn't alert anywhere). It definitely seems to be related to the same logging functionality, so I wanted to make sure it was a known issue before the development is over. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-283) Improve agent error reporting
Title: Message Title Russell Miller commented on PUP-283 Re: Improve agent error reporting I'd like to add my voice in the chorus of support for this, as I was the reason ENTERPRISE-618 was created. The specific result that I would like to see (and anything that gets us there) is to have something like an orange checkmark in the enterprise puppet console when a catalog succeeded, but it was a cached catalog. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-283) Improve agent error reporting
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-283 Improve agent error reporting Change By: Kenn Hussey Component/s: Client Add Comment 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/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Daniele Sluijters commented on an issue Re: Improve agent error reporting From my side as someone who consumes the PuppetDB API, I'd be pretty happy to see Christopher Price suggestions implemented. Right now one of the things that trip up people is that on a catalog compilation error no report is ever uploaded. Because of this nodes don't show up in tools like Puppetboard and worse, if they go undetected for a while can be automatically removed based on the node_ttl value. Yes monitoring but we all know how this goes. I'd like to see the second point too, knowing if the catalog compilation itself failed or it reached a timeout can be useful, especially in cases where people have a large/huge number of (exported) resources or depend on hoarding together an inordinate amount of concat fragments (Nagios servers come to mind). Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-283) Improve agent error reporting
Title: Message Title Joe Wagner commented on an issue Re: Improve agent error reporting Jason Antman I'm one of the PE UX designers and I'm very interested in this. It looks like there may be some confusion because a comment was added suggesting we close this ticket, but that comment was intended for another ticket. I would very much like to see what Christopher Price suggests made available. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... 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
Jira (PUP-283) Improve agent error reporting
Title: Message Title Daniel Dreier commented on an issue Re: Improve agent error reporting I made a trivial pull request to improve documentation on this command, but I think the issue can probably be closed at this point. Please re-open if you feel like further work is needed. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... 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/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Nate Wolfe commented on an issue Re: Improve agent error reporting Daniel Dreier Oops, I think you got the wrong ticket Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... 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/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Jason Antman commented on an issue Re: Improve agent error reporting To throw in some customer perspective here, FWIW: 1) I largely agree with what Christopher Price said. 2) There's a finite amount of information available from the agent about why a failure occurred. In most cases (i.e. excluding --profile) it's actually a pretty small amount of data. I don't see a compelling reason to not expose all of that in the reports themselves. If PE decides not to surface all of it to the user, oh well - I'm sure there are people other than myself that want as much detail as possible available to custom report processors, analytics, etc. and just because the PE UX team doesn't want to utilize it, doesn't mean the data should be thrown out (and yes, anything that exists only in a local text log file is, IMO, thrown out). 3) This is a seriously killer issue at the moment for those of us using PuppetDB and our own analytics and reporting (i.e. not the Dashboard) who want actually find out what happened on a node (or on a hundred nodes) without having to dig through logs. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-283) Improve agent error reporting
Title: Message Title Michelle Johansen commented on an issue Re: Improve agent error reporting Aaron Armstrong and Kenn Hussey We are taking this off the Platform team's list for now as Reporting and PuppetDB requests from PE are still in flux. If and when this work is needed, hopefully this work can be planned into the PE team workload with support from the PuppetDB and Platform team. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... 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
Jira (PUP-283) Improve agent error reporting
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-283 Improve agent error reporting Change By: Michelle Johansen Fix Version/s: 3.5.0 Add Comment 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.
