• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: ssh-slaves-plugin
• Labels:

  None
• Environment:

  Jenkins 2.54, running via the jenkins:2.54-alpine docker image. CentOS7 slaves with no pre-installed JDK.

1. 

   Screen Shot 2017-04-11 at 9.32.57 am.png

   36 kB

   2017-04-10 23:34

[JENKINS-43481] Jenkins 2.54 still downloads JDK1.7

Peter Lieverdink created issue - 2017-04-10 23:35

Peter Lieverdink made changes - 2017-04-10 23:37

Description

Original: When Jenkins starts remote slaves via SSH, it does not detect an installed java version and proceeds to download and install JDK7, which it no longer works with. This prevents the slaves from starting and Jenkins from working. I have configured a Java 1.8 JDK in the global tool config, but that seems to have made no difference. After removing both jdk.sh and jdk from $JENKINS_HOME on the slaves, the slave still installs JDK7. I have rolled back to v2.53, which still works fine. For reference, one of the slaves has JDK1.8.0 installed via the OS and *that* slave connects and runs fine.

New: When Jenkins starts remote slaves via SSH, it does not detect an installed java version and proceeds to download and install JDK7, which it no longer works with. This prevents the slaves from starting and Jenkins from working. I have configured a Java 1.8 JDK in the global tool config, but that seems to have made no difference. After removing both jdk.sh and jdk from $JENKINS_HOME on the slaves, the slave still installs JDK7. I have rolled back to v2.53, which still works fine. For reference, one of the slaves has JDK1.8.0 installed via the OS and *that* slave connects and runs ok.

Peter Lieverdink made changes - 2017-04-10 23:43

Component/s		New: ssh-slaves-plugin [ 15578 ]
Component/s	Original: core [ 15593 ]
Description	Original: When Jenkins starts remote slaves via SSH, it does not detect an installed java version and proceeds to download and install JDK7, which it no longer works with. This prevents the slaves from starting and Jenkins from working. I have configured a Java 1.8 JDK in the global tool config, but that seems to have made no difference. After removing both jdk.sh and jdk from $JENKINS_HOME on the slaves, the slave still installs JDK7. I have rolled back to v2.53, which still works fine. For reference, one of the slaves has JDK1.8.0 installed via the OS and *that* slave connects and runs ok.	New: When Jenkins starts remote slaves via SSH, it does not detect an installed java version and proceeds to download and install JDK7, which it no longer works with. This prevents the slaves from starting and Jenkins from working. I have configured a Java 1.8 JDK in the global tool config, but that seems to have made no difference. After removing both jdk.sh and jdk from $JENKINS_HOME on the slaves, the slave still installs JDK7. I have rolled back to v2.53, which still works fine. For reference, one of the slaves has JDK1.8.0 installed via the OS and *that* slave connects and runs ok. Edit: I changed the component to ssh-slaves-plugin, as that seems to be the culprit.

Oleg Nenashev made changes - 2017-04-11 09:17

Priority

Original: Major [ 3 ]

New: Critical [ 2 ]

Collapse comment: Daniel Beck added a comment - 2017-04-11 09:45

Daniel Beck added a comment - 2017-04-11 09:45

Right, Jenkins (well, SSH Slaves) only downloads a Java for the agent if there's no compatible Java detected. So workaround is to install a JRE 8.

Expand comment: Daniel Beck added a comment - 2017-04-11 09:45

Daniel Beck added a comment - 2017-04-11 09:45 Right, Jenkins (well, SSH Slaves) only downloads a Java for the agent if there's no compatible Java detected. So workaround is to install a JRE 8.

Collapse comment: Oleg Nenashev added a comment - 2017-04-11 09:52

Oleg Nenashev added a comment - 2017-04-11 09:52

So there are several pending fixes like https://github.com/jenkinsci/ssh-slaves-plugin/pull/43, which could help. We just need a hero, who would integrate the stuff

Expand comment: Oleg Nenashev added a comment - 2017-04-11 09:52

Oleg Nenashev added a comment - 2017-04-11 09:52 So there are several pending fixes like https://github.com/jenkinsci/ssh-slaves-plugin/pull/43 , which could help. We just need a hero, who would integrate the stuff

Collapse comment: Baptiste Mathus added a comment - 2017-04-11 10:48

Baptiste Mathus added a comment - 2017-04-11 10:48

Not assigning myself right now, to leave room for possible people to tackle this quicker, but I plan to look into it soonish. Also, I'm going to lower the priority as as Daniel explains there's an easy workaround.

Expand comment: Baptiste Mathus added a comment - 2017-04-11 10:48

Baptiste Mathus added a comment - 2017-04-11 10:48 Not assigning myself right now, to leave room for possible people to tackle this quicker, but I plan to look into it soonish. Also, I'm going to lower the priority as as Daniel explains there's an easy workaround.

Baptiste Mathus made changes - 2017-04-11 10:48

Priority

Original: Critical [ 2 ]

New: Major [ 3 ]

Oleg Nenashev made changes - 2017-04-11 11:31

Epic Link

New: JENKINS-43500 [ 180815 ]

Sascha Szott made changes - 2017-04-12 10:03

Link

New: This issue duplicates JENKINS-43492 [ JENKINS-43492 ]

Load more newer events