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") |
|||
| 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 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 probably because Jenkins and Maven pods are scheduled on different nodes. | |||
Revision as of 04:28, 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 probably because Jenkins and Maven pods are scheduled on different nodes.