[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-42011 Support bundle generation block at some situation when Jenkins is not responding Change By: Allan BURDAJEWICZ Assignee: Steven Christou Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178879.1487071677000.4606.1566171240176%40Atlassian.JIRA.
[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding
Title: Message Title Alvaro Lobato updated an issue Jenkins / JENKINS-42011 Support bundle generation block at some situation when Jenkins is not responding 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.32Steps 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42011) Support bundle generation block at some situation when Jenkins is not responding
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42011 Support bundle generation block at some situation when Jenkins is not responding Issue Type: Bug Assignee: Steven Christou Attachments: traceback (1).txt Components: support-core-plugin Created: 2017/Feb/14 11:27 AM Priority: 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.
