On Fri, Jun 9, 2017 at 7:51 AM Jesse Glick <[email protected]> wrote:
> You can bisect by Jenkins version number; or just check if 2.60 & 2.61
> work but 2.62 does not, implying that JENKINS-44120 is at fault.
>
>
I had 2.58 already defined in that docker instance, so I ran it. It failed
in what seemed to be the same way that 2.60.1-rc1 failed.
The Jenkins console log included the following output:
Jun 09, 2017 8:14:46 AM
hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler
uncaughtException
SEVERE: A thread (Thread-50/447) died unexpectedly due to an uncaught
exception, this may leave your Jenkins in a bad way and is usually
indicative of a bug in the code.
java.lang.NullPointerException
at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:447)
at
com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790)
at
com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502)
at java.lang.Thread.run(Thread.java:745)
The message when the agent fails to start says:
[06/09/17 08:17:19] [SSH] Opening SSH connection to mark-pc1.markwaite.net:22.
[06/09/17 08:17:19] [SSH] WARNING: The SSH key for this host does not
match the key required in the connection configuration. Connections
will be denied until until the host key matches the configuration key.
Key exchange was not finished, connection is closed.
java.io.IOException: There was a problem while connecting to
mark-pc1.markwaite.net:22
at com.trilead.ssh2.Connection.connect(Connection.java:834)
at com.trilead.ssh2.Connection.connect(Connection.java:703)
at com.trilead.ssh2.Connection.connect(Connection.java:617)
at
hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:785)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Key exchange was not finished,
connection is closed.
at
com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:95)
at
com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:237)
at com.trilead.ssh2.Connection.connect(Connection.java:786)
... 9 more
Caused by: java.io.IOException: The server hostkey was not accepted by
the verifier callback
at
com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:548)
at
com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790)
at
com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502)
... 1 more
[06/09/17 08:17:19] Launch failed - cleaning up connection
[06/09/17 08:17:19] [SSH] Connection closed.
The message claims that the host key is not correct, yet that same host key
is correct when used with the Jenkins 2.46.3 LTS build.
I'll check with 2.60, 2.61, and 2.62.
Mark Waite
> And of course we would want to improve
>
>
> https://github.com/jenkinsci/acceptance-test-harness/blob/786be14d7096e2d1464e6dd41e9e003a3e20906f/src/test/java/plugins/SshSlavesPluginTest.java#L75-L81
>
> to reproduce the issue, perhaps by creating variants of
>
>
> https://github.com/jenkinsci/docker-fixtures/tree/fe4f33921a290c352ad757a896bd570856ae062c/src/main/resources/org/jenkinsci/test/acceptance/docker/fixtures/SshdContainer
>
> that use different key formats (or whatever the problem turns out to be).
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3YkkfUbSW6CRt0N_JYJDw9xmWEvsp10AHJnJ0k6kP9_g%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFWBkJ5SfCkVsVmu0iZtvWtn2JsbkpHiGNrYzzJhB0AwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
