Hi,

we have found a problem with the calculation of "in_use_health_monitor" and "in_use_pool" of octavia in RHOSP17.1

Troubleshooting notes:

We found issues with cascading deletes of LBs:
Test1 (deleting pool with child items):

• created 1 LB with one listerner, one pool, one healthmonitor and 2 members
• deleted healthmonitor -> decreased in_use in database by one
• created new healthmonitor
• deleted pool: only in_use members were decreased by 2; in_use_pool and in_use_healthmonitors NOT decreased

--> deleting a pool with healthmonitors and members does not decrease in_use_pool and in_use_healthmonitors

Test2 (deleting empty pool):

• recreated pool with one healthmonitor and 2 members
• deleted healthmonitor -> decreased in_use by one
• tried to deleted 2 members: error - only one can be deleted. one member is deleted, in_use_member decreased by 1
• tried to delete leftover member: success, in_use_member decreased by 1
• deleted pool -> decreased in_use by one

--> deleting empty pool does decrease in_use_pool

Test3 (deleting LB with child items):

• recreated pool with one healthmonitor and 2 members
• deleted lb: in_use_lb, in_use_listener and in_use_members decreased; in_use_pool and in_use_healthmonitors NOT decreased

Result:
--> cascading delete of pool with child items (triggered by deleting pool itself or lb containing the pool) does not decrease in_use_healthmonitors and also in_use_pool

• deleting pools with healthmonitors and members (pool, healthmonitors not updated - members are updated)
• deleting LBs with any pool with healthmonitors and members (pool, healthmonitors not updated - members, listeners, lbs updated)

Checked in DB via 
select * from octavia.quotas where project_id="9ead2d655ce549feb2ec6d52b2ecfb12";

So if a customer delete and recreated ocativa LBs, he will run in quota errors soon.

You know something about this issue or a solution?

Thanks and kind regards,
Steffen

Describe the impact to you or the business
Customers running in quota issues and cant work anymore.