The fix for this merged last week, and the images are on brew-pulp. For example, brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/jenkins-slave-maven-rhel7:v3.10.0.20180515.215815 has the fix. To test: - you use a pipeline with agents like https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/maven-pipeline.yaml - log into the jenkins console, go to manage jenkins -> configure system, and update the maven pod template towards the bottom on the page by -- add the env var http_proxy to the pod template, setting it to a http proxy -- either a) change the image ref to brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/jenkins-slave-maven-rhel7:v3.10.0.20180515.215815, pull that image to the node, and uncheck pull always, so it uses the local image, or b) retag brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/jenkins-slave-maven-rhel7:v3.10.0.20180515.215815 to an image repository you can push, and then push it to an accessible repository - save the changes, - then start the build without the fix, things like the downloading of the remoting jar and access to the jnlp tunnel will fail in the resulting maven pod, as they try to go through the proxy and fail in fact, if you want to verify the problem exists, try a build with http_proxy set on the pod template and use the default image to start the build with the fix, the maven build should succeed like before
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1816