• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Component/s: core, ssh-credentials-plugin, ssh-slaves-plugin
• Labels:

  None

[JENKINS-19758] Jenkins: [reproducible] ssh slave log not available, spinning wheel after upgrading to SSH Credentials 1.4, SSH Slaves 1.2 and disconnecting/reconnecting

Steve Roth created issue - 2013-09-25 17:10

Steve Roth made changes - 2013-09-25 17:36

Description	Original: With a brand new Jenkins 1.532 install, no plugins, I am able to setup a slave fine, and see the slave log as I disconnect/reconnect. This is using Credentials Plugin 1.4, SSH Credentials Plugin 0.3, SSH Slaves Plugin 0.25 When I update to use Credentials Plugin 1.8.2 and restart, everything continues working fine. But when I update to use SSH Credentials Plugin 1.4, SSH Slaves Plugin 1.2 I see a regression -- when I disconnect/reconnect, then click on Log to view the slave logfile, I just see a spinning wheel in the browser. I can tell the slave did successfully connect (since I see 1 executor available), but I cannot see any slave output. This is a pretty major issue when used in a virtualized slaves environment, since this makes it very difficult to understand the status of the slaves and to troubleshoot slave connection issues.	New: With a brand new Jenkins 1.532 install, no plugins, I am able to setup a slave fine, and can see the slave logfile when I disconnect/reconnect. This is using Credentials Plugin 1.4, SSH Credentials Plugin 0.3, SSH Slaves Plugin 0.25 When I update to use Credentials Plugin 1.8.2 and restart, this process continues working fine. But when I update to use SSH Credentials Plugin 1.4, SSH Slaves Plugin 1.2 I see a regression -- when I disconnect/reconnect, then click on Log to view the slave logfile, I just see a spinning wheel in the browser. I can tell the slave did successfully connect (since I see 1 executor available), but I cannot see any slave log output. I can consistently reproduce this issue. This is a pretty major issue when used in a virtualized slaves environment, since this makes it very difficult to understand the status of the slaves and to troubleshoot slave connection issues.
Summary	Original: Jenkins: ssh slave log not available, spinning wheel after upgrading to SSH Credentials 1.4, SSH Slaves 1.2	New: Jenkins: [reproducible] ssh slave log not available, spinning wheel after upgrading to SSH Credentials 1.4, SSH Slaves 1.2 and disconnecting/reconnecting

Steve Roth made changes - 2013-09-25 17:41

Description

Original: With a brand new Jenkins 1.532 install, no plugins, I am able to setup a slave fine, and can see the slave logfile when I disconnect/reconnect. This is using Credentials Plugin 1.4, SSH Credentials Plugin 0.3, SSH Slaves Plugin 0.25 When I update to use Credentials Plugin 1.8.2 and restart, this process continues working fine. But when I update to use SSH Credentials Plugin 1.4, SSH Slaves Plugin 1.2 I see a regression -- when I disconnect/reconnect, then click on Log to view the slave logfile, I just see a spinning wheel in the browser. I can tell the slave did successfully connect (since I see 1 executor available), but I cannot see any slave log output. I can consistently reproduce this issue. This is a pretty major issue when used in a virtualized slaves environment, since this makes it very difficult to understand the status of the slaves and to troubleshoot slave connection issues.

New: With a brand new Jenkins 1.532 install, no plugins, I am able to setup a dumb ssh slave fine, and can see the slave logfile when I disconnect/reconnect and click Log. This is using Credentials Plugin 1.4, SSH Credentials Plugin 0.3, SSH Slaves Plugin 0.25 When I update to use Credentials Plugin 1.8.2 and restart, this process continues working fine. So far so good. But when I update to use SSH Credentials Plugin 1.4, SSH Slaves Plugin 1.2 I see a regression -- when I disconnect/reconnect, then click on Log to view the slave logfile, I just see a spinning wheel in the browser. I can tell the slave did successfully connect (since I see 1 executor available), but I cannot see any slave log output. I can consistently reproduce this issue. This is a pretty major issue when used in a virtualized slaves environment, since this makes it very difficult to understand the status of the slaves and to troubleshoot slave connection issues.

Steve Roth made changes - 2013-09-25 17:44

Description

Original: With a brand new Jenkins 1.532 install, no plugins, I am able to setup a dumb ssh slave fine, and can see the slave logfile when I disconnect/reconnect and click Log. This is using Credentials Plugin 1.4, SSH Credentials Plugin 0.3, SSH Slaves Plugin 0.25 When I update to use Credentials Plugin 1.8.2 and restart, this process continues working fine. So far so good. But when I update to use SSH Credentials Plugin 1.4, SSH Slaves Plugin 1.2 I see a regression -- when I disconnect/reconnect, then click on Log to view the slave logfile, I just see a spinning wheel in the browser. I can tell the slave did successfully connect (since I see 1 executor available), but I cannot see any slave log output. I can consistently reproduce this issue. This is a pretty major issue when used in a virtualized slaves environment, since this makes it very difficult to understand the status of the slaves and to troubleshoot slave connection issues.

New: With a brand new Jenkins 1.532 install, no plugins, I am able to setup a dumb ssh slave fine, and can see the slave logfile when I disconnect/reconnect and click Log. This is using Credentials Plugin 1.4, SSH Credentials Plugin 0.3, SSH Slaves Plugin 0.25 When I update to use Credentials Plugin 1.8.2 and restart, this process continues working fine. So far so good. But when I update to use SSH Credentials Plugin 1.4, SSH Slaves Plugin 1.2 I see a regression -- when I disconnect/reconnect, then click on Log to view the slave logfile, I just see a spinning wheel in the browser. I can tell the slave did successfully connect (since I see 1 executor available), but I cannot see any slave log output. I can consistently reproduce this issue. This is a pretty major issue when used in a virtualized slaves environment where slaves are disconnected, reset, and reconnected, since this makes it very difficult to understand the status of the slaves and to troubleshoot slave connection issues.

Corneil du Plessis made changes - 2013-10-08 15:32

Priority

Original: Major [ 3 ]

New: Blocker [ 1 ]

Stephen Connolly made changes - 2013-10-08 15:44

Component/s

New: core [ 15593 ]

SCM/JIRA link daemon made changes - 2013-10-08 16:47

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Stephen Connolly made changes - 2013-10-09 11:30

Link

New: This issue is duplicated by JENKINS-19026 [ JENKINS-19026 ]

Costin Caraivan made changes - 2013-10-15 11:48

Resolution	Original: Fixed [ 1 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Daniel Beck made changes - 2014-09-22 20:42

Resolution		New: Fixed [ 1 ]
Status	Original: Reopened [ 4 ]	New: Resolved [ 5 ]

Stephen Connolly made changes - 2016-07-13 09:05

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Load more newer history items