origin: using targetPort with a name in service definition doesn't seem to work via route

Using targetPort in the service definition to map to a named port in a pod definition doesn’t seem to work. Everything looks like it works and the web interface even has 80/TCP → apacheport in the display, but I can never establish a connection. If I instead use targetPort : 8080 in openshift it works. Mapping to a name works in kubernetes-1.1.0-0.17.git388061f.fc23.x86_64 so I think I’m not doing something wrong, but I can’t be sure. My target ose environment is 3.1.

Example Pod

{
    "apiVersion": "v1",
    "kind": "Pod",
    "metadata": {
        "labels": {
            "app": "helloapache"
        },
        "name": "helloapache"
    },
    "spec": {
        "containers": [
            {
                "image": "dustymabe/httpd:latest",
                "name": "helloapache",
                "ports": [
                    {
                        "name": "apacheport",
                        "containerPort": 8080,
                        "protocol": "TCP"
                    }
                ]
            }
        ]
    }
}

Example service

{
    "apiVersion": "v1",
    "kind": "Service",
    "metadata": {
        "labels": {
            "name": "apacheservice"
        },
        "name": "apacheservice"
    },
    "spec": {
        "ports": [
            {
                "port": 80,
                "targetPort": "apacheport"
            }
        ],
        "selector": {
            "app": "helloapache"
        },
        "type": "LoadBalancer"
    }
}