OpenShift Jenkins fails to Communicate with Maven slaves

From NovaOrdis Knowledge Base
Revision as of 21:10, 15 May 2018 by Ovidiu (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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.