Description of problem:
User can specified custom partition and path when creating F5 router pod, that means the vserver has been created in the partition and path, but it will failed to create F5 router and pod logs shows error: "The requested Virtual Server (/Ocp/ocp-http-vserver) was not found." Actually, the vserver should be in /Ocp/path/ocp-http-vserver, the "path" is missing when request the vserver.

Workaround is add path in front of the vserver name, for example:
oadm router f5router --type=f5-router \ 
--external-host-http-vserver=path/ocp-http-vserver \
--external-host-https-vserver=path/ocp-https-vserve \
--external-host-partition-path=Ocp/path \
<---snip--->

but it might confusing user since they have specified the path in option --external-host-partition-path.
 

Version-Release number of selected component (if applicable):
openshift v3.6.125
kubernetes v1.6.1+5115d708d7
etcd 3.2.0

How reproducible:
always

Steps to Reproduce:
1. oadm router f5router --replicas=1 --type=f5-router --external-host=10.x.x.x --external-host-username=user --external-host-password=password --external-host-http-vserver=path/ocp-http-vserver --external-host-https-vserver=path/ocp-https-vserver --external-host-private-key=/root/.ssh/id_rsa  --service-account=router --external-host-insecure=true --external-host-internal-ip=10.x.x.x --external-host-vxlan-gw=10.130.0.1/14 --external-host-partition-path=Ocp/path
2.
3.

Actual results:
should add path in front of the vserver name, otherwise will failed to start F5 router pod.

Expected results:
needn't to add extra path in front of the vserver name, just like: 
--external-host-http-vserver=ocp-http-vserver
--external-host-https-vserver=ocp-https-vserver
--external-host-partition-path=Ocp/path

Additional info: