[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding

0 views
Skip to first unread message

alobato@cloudbees.com (JIRA)

unread,
Feb 14, 2017, 6:28:03 AM2/14/17
to jenkinsc...@googlegroups.com
Alvaro Lobato created an issue
 
Jenkins / Bug JENKINS-42011
Support bundle generation block at some situation when Jenkins is not responding
Issue Type: Bug Bug
Assignee: Steven Christou
Attachments: traceback (1).txt
Components: support-core-plugin
Created: 2017/Feb/14 11:27 AM
Priority: Major Major
Reporter: Alvaro Lobato

There are situations where a Jenkins instance is not responding properly and before restarting it we request a support bundle to have the maximum diagnosis information possible.
ie. If there is a blocked remote channel to an agent the support bundle will not be generated, as it will block trying to get information from that agent, and the user will be forced to restart without a support bundle.
See attached stacktrace with an example.
We should add a timeout to each operation we perform on the support bundled to make sure we get at least some information when Jenkins is not responding.
This happened on 2.32

Steps to reproduce:
1. Somehow hang a remoting channel?
2. Take a support bundle.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

alobato@cloudbees.com (JIRA)

unread,
Feb 14, 2017, 6:31:01 AM2/14/17
to jenkinsc...@googlegroups.com
Alvaro Lobato updated an issue
Change By: Alvaro Lobato
There are situations where a Jenkins instance is not responding properly and before restarting it we request a support bundle to have the maximum diagnosis information possible.
ie. If there is a blocked remote channel to an agent the support bundle will not be generated, as it will block trying to get information from that agent, and the user will be forced to restart without a support bundle.
See attached stacktrace with an example.
We should add a timeout to each operation we perform on the support bundled to make sure we get at least some information when Jenkins is not responding.
This happened on 2.32

Steps to reproduce:
1. Somehow hang a remoting channel ? . In this case it was a plugin transferring huge amounts of data + maybe some connectivity issues.
2. Take a support bundle.

aburdajewicz@cloudbees.com (JIRA)

unread,
Aug 18, 2019, 7:34:01 PM8/18/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ
Change By: Allan BURDAJEWICZ
Assignee: Steven Christou Allan BURDAJEWICZ
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages