Bug 1395153

Description of problem:
the route is unreachable via F5 server if the route name is different from the service name.


Version-Release number of selected component (if applicable):
openshift v3.4.0.26+f7e109e
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0


How reproducible:
always

Steps to Reproduce:
1. oadm router f5router...
2. create pod and service
3. create route which route name is different from service name, like below:

[root@hongli-f5-master ~]# oc get route -n u1p1
NAME               HOST/PORT                                                PATH      SERVICES           PORT      TERMINATION
myroute            www.example.com                                                    service-unsecure   http      

Actual results:
Failed to curl the route.
#curl --resolve www.example.com:80:192.168.55.116 http://www.example.com
curl: (56) Recv failure: Connection reset by peer


Expected results:
curl should be successful


Additional info:
1. no this issue in v3.2.2.2 f5-router image
2. v3.3.1.4 f5-router image also has this issue
3. it is ok if route name same to service name, see example below (both name are called "service-unsecure")

NAME               HOST/PORT                                                PATH      SERVICES           PORT      TERMINATION
service-unsecure   www.example.com                                                    service-unsecure   http      

Then curl can get the result as expected:
curl --resolve www.example.com:80:192.168.55.116 http://www.example.com
Hello-OpenShift-1 http-8080