-
Bug
-
Resolution: Fixed
-
Major
-
archlinux x86_64 running in Virtualbox VM
jenkins version 1.596
Linux 3.18.2-2-ARCH
pluin list: all are their most current version per checking for update need before posting this.
Ant Plugin
Credentials Plugin
CVS Plug-in
Email Extension PluginExclusive
Execution Plugin
External Monitor Job Type Plugin
GIT client plugin
GIT plugin
GitHub API Plugin
GitHub plugin
Javadoc Plugin
JUnit Plugin
LDAP Plugin
Mailer Plugin
MapDB API Plugin
Matrix Authorization Strategy Plugin
Matrix Project Plugin
Maven Integration plugin
OWASP Markup Formatter Plugin
PAM Authentication plugin
SCM API Plugin
Script Security Plugin
SSH Credentials Plugin
SSH Slaves plugin
Subversion Plug-in
Token Macro Plugin
Translation Assistance plugin
VirtualBox Plugin
Windows Slaves Plugin
archlinux x86_64 running in Virtualbox VM jenkins version 1.596 Linux 3.18.2-2-ARCH pluin list: all are their most current version per checking for update need before posting this. Ant Plugin Credentials Plugin CVS Plug-in Email Extension PluginExclusive Execution Plugin External Monitor Job Type Plugin GIT client plugin GIT plugin GitHub API Plugin GitHub plugin Javadoc Plugin JUnit Plugin LDAP Plugin Mailer Plugin MapDB API Plugin Matrix Authorization Strategy Plugin Matrix Project Plugin Maven Integration plugin OWASP Markup Formatter Plugin PAM Authentication plugin SCM API Plugin Script Security Plugin SSH Credentials Plugin SSH Slaves plugin Subversion Plug-in Token Macro Plugin Translation Assistance plugin VirtualBox Plugin Windows Slaves Plugin
Setting up a VM with VirtualBox fails with ssh issues. I have confirmed it is not an issue with my key by logging into the Jenkins install and using the same user it does was able to ssh to the VirtualBox machine without any issue. I tried an ssh key with and without a password both fail in jenkins the same way. Both ways work if manually done as the jenkins user to login through ssh to the running vm.
The key size and type
rsa 16384 with no rounds on password.
error:
[VirtualBox] Launching node testbox
[VirtualBox] Powering up VirtualBoxMachine{host=VirtualBoxHost
,name='testbox'}...
[VirtualBox] Lost connection to http://vboxmain:18083, reconnecting
[VirtualBox] Trying to connect to http://vboxmain:18083, user
[VirtualBox] Creating connection to VirtualBox version 4.3.20_OSE
[VirtualBox] Connected to VirtualBox version 4.3.20_OSE on host http://vboxmain:18083
[VirtualBox] node testbox in state Running
[VirtualBox] node testbox started
[VirtualBox] Sleep before stage 2 launcher, attempt 1
[VirtualBox] Starting stage 2 launcher (SSHLauncher)
[01/19/15 17:17:13] [SSH] Opening SSH connection to :22.
Key exchange was not finished, connection is closed.
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
java.lang.IllegalStateException: Connection is not established!
at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:1030)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:207)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:169)
at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1173)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[01/19/15 17:17:13] Launch failed - cleaning up connection
[01/19/15 17:17:13] [SSH] Connection closed.
- is related to
-
JENKINS-33021 trilead ssh MAC and key exchange algorithms severely outdated
- Resolved