使用SSH-Agent在jenkins中配置從屬節點

Question

您好everubody，當我想使用SSH-agent方法在jenkins中配置一個從屬節點時遇到此問題，您能幫助我解決此問題嗎？

11/01/17 12:16:15] [SSH] Opening SSH connection to 192.168.226.197:22.
/var/lib/jenkins/.ssh/known_hosts [SSH] No Known Hosts file was found at /var/lib/jenkins/.ssh/known_hosts. Please ensure one is created at this path and that Jenkins can read it.
Key exchange was not finished, connection is closed.
java.io.IOException: There was a problem while connecting to 192.168.226.197: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:1284)
    at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:804)
    at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)
    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: 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
[11/01/17 12:16:15] Launch failed - cleaning up connection
[11/01/17 12:16:15] [SSH] Connection closed.

Answer 1

在您的代理配置中，對於“ 主機密鑰驗證策略 ”，您可能具有“ 已知主機文件驗證策略 ”。 但是當master啟動ssh連接時-它不會更新已知的主機文件。 因此，您可以嘗試手動執行ssh命令以啟動連接並適當地更新文件。

當然，您可以通過設置“ 非驗證驗證策略 ”來禁用“ 知道主機文件驗證策略 ”，但這是不安全的 。

Answer 2

在/var/lib/jenkins/.ssh/known_hosts中找不到“ 未知主機”文件。 請確保在此路徑上創建了一個，並且詹金斯可以讀取它。

在主計算機上，可以使用ssh-copy-id命令連接到代理：

ssh-copy-id [-p agent-ssh-port] agent-user@agent-hostname

在主服務器上，在Jenkins Nodes中重新啟動代理。