Description of problem:
Build a custom slave image, and using jenkins as S2i builder, after trigger job in the jenkins webconsle, the slave pod can't be running with below error:

Jul 19, 2016 11:27:50 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to 172.30.166.34:50000 (retrying:3)
java.net.NoRouteToHostException: No route to host
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at java.net.Socket.connect(Socket.java:538)
        at hudson.remoting.Engine.connect(Engine.java:383)
        at hudson.remoting.Engine.run(Engine.java:298)


Version-Release number of selected component (if applicable):
openshift3/jenkins-1-rhel7 (imageid 1e3f32968b5a)
openshift v3.3.0.6
kubernetes v1.3.0+57fb9ac

How reproducible:
always

Steps to Reproduce:
1. Create a new project and add edit role.
2.Build a new custom slave image
$ oc new-app  https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/master-slave/jenkins-slave-template.json  -p IMAGE_NAME=$registry/rhscl/ruby-22-rhel7:latest,IMAGE_STREAM_NAME=ruby22,SLAVE_REPO_URL=https://github.com/xiuwang/jenkins-slave-rhel7repo,SLAVE_REPO_CONTEXTDIR=
3.Create jenkins master pod included the custom slave image label
oc new-app  -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/master-slave/jenkins-master-template.json

4.Login jenkins webconsole, go to ruby-hellow-world-test project configuration page, change to use ruby22 label
 5.Start a build in the jenkins console.
 6.Check slave pod.

Actual results:
  #1
(pending—All nodes of label ‘ruby22’ are offline) 
And description error in the slave pod logs.

Expected results:

Should no error in slave pod, and could build successfully.


Additional info: