OpenShift Jenkins fails to Communicate with Maven slaves: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
=Overview=
=Overview=


The pipeline does not progress because the Mavne pods initiated by Jenkins fail to "call back":
The pipeline does not progress because the Maven pods initiated by Jenkins fail to "call back":


  curl: (7) Failed connect to 172.30.176.127:80; No route to host
  curl: (7) Failed connect to 172.30.176.127:80; No route to host


This is probably because Jenkins and Maven pods are scheduled on different nodes.
This is was caused by OpenShift trying to schedule the Maven pods on different nodes that the one running Jenkins.
 
I worked around by by removing a node. This is not a correct solution- it invocations should be routed across nodes.

Latest revision as of 21:10, 15 May 2018

Internal

Overview

The pipeline does not progress because the Maven pods initiated by Jenkins fail to "call back":

curl: (7) Failed connect to 172.30.176.127:80; No route to host

This is was caused by OpenShift trying to schedule the Maven pods on different nodes that the one running Jenkins.

I worked around by by removing a node. This is not a correct solution- it invocations should be routed across nodes.