-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Minor
-
Component/s: ssh-slaves-plugin, trilead-api-plugin
-
None
-
Environment:Jenkins ver. 1.651.3, 2.150.1
ssh-slaves-plugin:1.11-1.30.1
OS: Linux 2.6.32-642.11.1.el6.x86_64
Attempting to start Linux node results in failure:
{{08/16/18 17:47:31] [SSH] Copying latest slave.jar...}}
{{hudson.util.IOException2: Could not copy slave.jar into '/build' on slave}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1054)}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:137)}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:723)}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)}}
{{Â Â Â Â Â Â Â at java.util.concurrent.FutureTask.run(FutureTask.java:266)}}
{{Â Â Â Â Â Â Â at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}}
{{Â Â Â Â Â Â Â at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}}
{{Â Â Â Â Â Â Â at java.lang.Thread.run(Thread.java:748)}}
{{Caused by: hudson.util.IOException2: Could not copy slave.jar to '/build/slave.jar' on slave}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1049)}}
{{Â Â Â Â Â Â Â ... 7 more}}
{{Caused by: com.trilead.ssh2.SFTPException: Failure (SSH_FX_FAILURE: An error occurred, but no specific error code exists to describe the failure.)}}
{{Â Â Â Â Â Â Â at com.trilead.ssh2.SFTPv3Client.openFile(SFTPv3Client.java:1201)}}
{{Â Â Â Â Â Â Â at com.trilead.ssh2.SFTPv3Client.createFile(SFTPv3Client.java:1074)}}
{{Â Â Â Â Â Â Â at com.trilead.ssh2.SFTPv3Client.createFile(SFTPv3Client.java:1055)}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SFTPClient.writeToFile(SFTPClient.java:93)}}
{{Â Â Â Â Â Â Â at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1039)}}
{{Â Â Â Â Â Â Â ... 7 more}}
Turns out root cause is file system went read-only:
mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
      It's possible that information reported by mount(8) is not
      up to date. For actual information about system mount points
      check the /proc/mounts file.
Reporting error because of the response in the logs:
(SSH_FX_FAILURE: An error occurred, but no specific error code exists to describe the failure.)
This is a different failure condition to other documented bugs (JENKINS-42856 , JENKINS-42441) so worth mentioning and perhaps code can be fixed to provide more descriptive failure response
