OpenShift Jenkins fails to Communicate with Maven slaves: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * OpenShift CI/CD Operations") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[OpenShift_CI/CD_Operations#Troubleshooting|OpenShift CI/CD Operations]] | * [[OpenShift_CI/CD_Operations#Troubleshooting|OpenShift CI/CD Operations]] | ||
=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. | |||
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.