Jira (PUP-5957) add a flag to puppet agent that helps user submit a server stacktrace

2 views
Skip to first unread message

Henrik Lindberg (JIRA)

unread,
Feb 22, 2016, 11:58:02 AM2/22/16
to puppe...@googlegroups.com
Henrik Lindberg created an issue
 
Puppet / New Feature PUP-5957
add a flag to puppet agent that helps user submit a server stacktrace
Issue Type: New Feature New Feature
Assignee: Unassigned
Created: 2016/02/22 8:57 AM
Priority: Normal Normal
Reporter: Henrik Lindberg

Users have problems sending a stack trace from the master when they encounter an error on the agent for a compilation that ended with an error on the master side.

The absolute most convenient would be for the user to run with

puppet agent -t --jira=PUP-6666

And that would then instruct the server to turn on trace, run, and send the trace output to the agent. The agent then sends it to the jira ticket as an attachment (using the JIRA API). The user will always be prompted if they want to send or if they just want the file. If sending, they are prompted for their jira user name and password.

Simpler versions would just dump the file. Even simpler, the file is found on the server, the agent gets the location of the file in the error message.

This would help with the problem of often having to ask 2-3 times before the user is able to submit the needed information.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

Henrik Lindberg (JIRA)

unread,
Feb 22, 2016, 11:59:04 AM2/22/16
to puppe...@googlegroups.com
Henrik Lindberg commented on New Feature PUP-5957
 
Re: add a flag to puppet agent that helps user submit a server stacktrace

Ping Kylo Ginsberg some work on the server side too, but mostly client. PE users have the support script, for FOSS there is nothing.

Jonathan Gray (JIRA)

unread,
Feb 22, 2016, 12:03:03 PM2/22/16
to puppe...@googlegroups.com
Jonathan Gray commented on New Feature PUP-5957

Automatic submission would be nice, but you have to take into account that a user may need to scrub that output for site-specific data. For instance a hiear-eyaml lookup which may contain a secret in plaintext, or that the user just doesn't want their company information attached to a google indexed PUP.

Rob Nelson (JIRA)

unread,
Feb 22, 2016, 12:08:04 PM2/22/16
to puppe...@googlegroups.com
Rob Nelson commented on New Feature PUP-5957

If possible, it could send a request to the OS to open a browser window pointing to the JIRA ticket, with a code block pre-populated. The user could then scrub the code and add verbiage before clicking Add.

For remote systems (ssh'ed into the master, for instance), trying to open such a browser window may be pointless. In that case, a URL should be displayed at the end so the user can C&P it. If the comment textbox can be pre-populated, great; if not, hopefully the cursor could be in the textbox.

Henrik Lindberg (JIRA)

unread,
Feb 22, 2016, 12:20:03 PM2/22/16
to puppe...@googlegroups.com

You can also email to jira - the server could send that email. When it comes to information, it is really the stack trace we are after which only contains names of ruby files and linenumbers + the actual error, so it should be easy for someone to look at the data and replace anything sensitive - it is not the full log we are after.

Jonathan Gray (JIRA)

unread,
Feb 22, 2016, 12:24:03 PM2/22/16
to puppe...@googlegroups.com
Jonathan Gray commented on New Feature PUP-5957

It would also be super nice if issuing said command would grab the trace without the need to restart the server daemon in debug mode. That would also keep the amount of information needing to be potentially scrubbed down significantly because it would only contain the information for that agent run.

Henrik Lindberg (JIRA)

unread,
Feb 22, 2016, 12:37:02 PM2/22/16
to puppe...@googlegroups.com

The trace is what is most valuable when the server errors - the debug output is more for figuring out when something computes, but not the expected way (in my experience those problems are rarely caused by a puppet bug).

Henrik Lindberg (JIRA)

unread,
Feb 22, 2016, 12:40:24 PM2/22/16
to puppe...@googlegroups.com

Even something really simple like --servertrace where the server sends a trace back and it gets displayed by the agent would help a lot. User can then do what is needed with that information.

Jonathan Gray (JIRA)

unread,
Feb 22, 2016, 12:50:07 PM2/22/16
to puppe...@googlegroups.com
Jonathan Gray commented on New Feature PUP-5957

Even better, wrap the current --trace option's output with metadata about if it's from the agent or server then you don't have to care about where the error actually occurs as a user.

Henrik Lindberg (JIRA)

unread,
May 15, 2017, 2:40:05 PM5/15/17
to puppe...@googlegroups.com
Henrik Lindberg updated an issue
 
Change By: Henrik Lindberg
Labels: triaged
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Geoff Nichols (JIRA)

unread,
May 25, 2017, 1:21:04 PM5/25/17
to puppe...@googlegroups.com

Josh Cooper (Jira)

unread,
May 17, 2023, 2:18:03 PM5/17/23
to puppe...@googlegroups.com
Josh Cooper commented on New Feature PUP-5957
 
Re: add a flag to puppet agent that helps user submit a server stacktrace

For security reasons we don't want server side exceptions to be automatically sent from the server to the agent, so I'm going to close this.

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Atlassian logo

Josh Cooper (Jira)

unread,
May 17, 2023, 2:19:03 PM5/17/23
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages