|
This plugin was able to establish the connection to vRealize Orchestrator that was on version 7.0. However our team has just upgraded vRealize Orchestrator to 7.0.1 and then we immediately see the following build error:
10:37:55 FATAL: Received fatal alert: handshake_failure
10:37:55 java.io.IOException: Received fatal alert: handshake_failure
10:37:55 at com.vmware.vro.jenkins.plugin.OrchestratorBuilder.perform(OrchestratorBuilder.java:95)
10:37:55 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
10:37:55 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
10:37:55 at hudson.model.Build$BuildExecution.build(Build.java:205)
10:37:55 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
10:37:55 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
10:37:55 at hudson.model.Run.execute(Run.java:1738)
10:37:55 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
10:37:55 at hudson.model.ResourceController.execute(ResourceController.java:98)
10:37:55 at hudson.model.Executor.run(Executor.java:410)
10:37:55 Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
10:37:55 at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
10:37:55 at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
10:37:55 at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1959)
10:37:55 at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1077)
10:37:55 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)
10:37:55 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)
10:37:55 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1323)
10:37:55 at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:395)
10:37:55 at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:354)
10:37:55 at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
10:37:55 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
10:37:55 at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
10:37:55 at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
10:37:55 at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
10:37:55 at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
10:37:55 at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
10:37:55 at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
10:37:55 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
10:37:55 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
10:37:55 at com.vmware.vro.jenkins.plugin.util.RestClient.executeRequest(RestClient.java:139)
10:37:55 at com.vmware.vro.jenkins.plugin.util.RestClient.httpGet(RestClient.java:77)
10:37:55 at com.vmware.vro.jenkins.plugin.OrchestratorClient.fetchWorkflows(OrchestratorClient.java:66)
10:37:55 at com.vmware.vro.jenkins.plugin.OrchestratorBuilder.perform(OrchestratorBuilder.java:87)
10:37:55 ... 9 more
10:37:55 [BFA] Scanning build for known causes...
10:37:55 [BFA] No failure causes found
10:37:55 [BFA] Done. 0s
10:37:55 Started calculate disk usage of build
10:37:55 Finished Calculation of disk usage of build in 0 seconds
10:37:55 Started calculate disk usage of workspace
10:37:55 Finished Calculation of disk usage of workspace in 0 seconds
10:37:55 Finished: FAILURE
Anyone has any idea how to solve this?
p.s. We've seen this error message even in the job configuration page. I've attached a screenshot of this.
|
