Red Hat Bugzilla – Bug 1287062
F5 router failed to delete pool during removing Pod because it is in use by a policy action
Last modified: 2016-04-12 15:14:37 EDT
When we try to delete Pod, F5 router failed to delete BIGIP's pool with error messages below
[email@example.com ~]# oc logs router-1-yilp0
E1130 01:34:19.783032 1 controller.go:99] Encountered an error on DELETE request to URL https://172.30.62.90/mgmt/tm/ltm/pool/openshift_aaaaa-xxx1_yyy: HTTP code: 400; error from F5: 01070265:3: The Pool (/Common/openshift_xxxxxx-yyyyy_zzzz) cannot be deleted because it is in use by a policy action (/Common/openshift_insecure_routes openshift_route_xxxxxx-yyyyy_zzzz 0).
E1130 01:35:49.499131 1 controller.go:83] Encountered an error on POST request to URL https://172.30.62.90/mgmt/tm/ltm/virtual/XXXXXX-443/profiles: HTTP code: 400; error from F5: 0107149c:3: Virtual server /Common/XXXXXX-443 has more than one clientssl/serverssl profile but none of them is default for SNI.
@knakayam did the route have just a single pod / endpoint? For a single pod case, the error is benign in that we try to delete the pool if the number of endpoints is 0 (when a route which has a single pod and the pod is deleted). The same action is also done when a route is deleted, so the pool will be cleaned up when the route gets deleted (if it does).
The reason we do the delete on the last endpoint is because a pool may not be associated with a route (only a service exists) and we don't want the pool hanging around as will never get deleted if there is no route.