Description of problem: create pod, service and route, make sure the route can be reached via F5 server. Then delete the service, but the route still can be reached. Checked the pools and polices on F5, found that the service was not removed from the pools after deleting service. 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, service and route. #oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/routing/list_for_pods.json #oc expose svc service-unsecure 3. curl the route. #curl --resolve $route:80:$f5-ip http://$route 4. delete the service #oc delete sve servie-unsecure 5. repeat step 3 Actual results: the route can be reached in both step3 and step5. Expected results: the route should be unreachable in step5 since the service and endpoint has been deleted. Additional info: after deleting the service, no endpoints for the route [root@hongli-34-master ~]# oc describe route Name: service-unsecure Namespace: u1p1 Created: 2 hours ago Labels: name=service-unsecure Annotations: openshift.io/host.generated=true Requested Host: service-unsecure-u1p1.router.default.svc.cluster.local exposed on router f5router 2 hours ago Path: <none> TLS Termination: <none> Insecure Policy: <none> Endpoint Port: http Service: service-unsecure Weight: 100 (100%) Endpoints: <error: endpoints "service-unsecure" not found>
Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/b1d8e0b9ede8d7684e84fa50d99887c8c9d26f2d Fixes bug 1395545 [link](https://bugzilla.redhat.com/show_bug.cgi?id=1395545) empty the pool, or delete the pool when endpoints are deleted
3.4 cherry-pick PR https://github.com/openshift/origin/pull/11956
This has been merged into ocp and is in OCP v3.4.0.28 or newer.
verified in OCP v3.4.0.28, the bug has been fixed.
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-2017:0066