unable to delete wrongly configured lbaas pool

If lbaas pool was created with unsupported balancing algorithm or protocol, there will be a corresponding error message from plugin:

ubuntu@devstack:~$ neutron lbaas-pool-create --lb-algorithm SOURCE_IP --loadbalancer 6001b5fc-44ba-451c-aba0-acb181ae1759 --protocol HTTP
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Driver error: {"message":"Failed to Create(id {\n msb: 13026752061630139032\n lsb: 9611772928562201250\n}\ntenant_id: \"9ed00fdeea2441a19403460cb82720b0\"\nname: \"\"\ndescription: \"\"\nadmin_state_up: true\nloadbalancers {\n id {\n msb: 6918010597707236636\n lsb: 12367074455144240985\n }\n}\nprotocol: HTTP\n); Unsupported protocol: HTTP","code":400}
Neutron server returns request_ids: ['req-68aa2d91-6c05-4253-bc6e-0d0dc36ae6fe']

Neutron will still add this pool to database, and it will not be possible to delete it, since plugin will try to delete it from midonet first, and since it is not there initially, 404 will be returned and request will fail.

ubuntu@devstack:~$ neutron lbaas-pool-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
+--------------------------------------+------+--------------+----------+----------------+
| id | name | lb_algorithm | protocol | admin_state_up |
+--------------------------------------+------+--------------+----------+----------------+
| b4c851fb-3a8d-4a98-8563-e08d9caa82a2 | | SOURCE_IP | HTTP | True |
+--------------------------------------+------+--------------+----------+----------------+
ubuntu@devstack:~$ neutron lbaas-pool-delete b4c851fb-3a8d-4a98-8563-e08d9caa82a2
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Driver error: {"message":"There is no Pool with ID b4c851fb-3a8d-4a98-8563-e08d9caa82a2.","code":404}
Neutron server returns request_ids: ['req-9360dab6-9db6-45b4-8d17-6d81a8638e5b']

Only way to delete this kind of pool is to delete it from database manually.

Maybe, 404 midonet api condition with delete request should be handled in other way, not throwing the error, since we want to delete something that is not there initially.