OpenShift Jenkins fails to Communicate with Maven slaves: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
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 | 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. | |||
Revision as of 05:33, 22 November 2017
Internal
Overview
The pipeline does not progress because the Mavne 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.