Comment 3 for bug 1830943

Tempest cleanup works with two types of services, project ones [1] and global ones [2]. First cleanup iterates over the projects which are not in saved_state.json and removes all resources related to that projects. Then it iterates over the global services and removes them.

If a resource is associated with a project which has been already removed and the resource is from project services category, it won't be cleaned.
I tried to run some of the manila tests and after cleanup I ended up with 50 networks which were associated with already non-existing projects and therefore they weren't cleaned. I guess this could happen if a test case removes a project but doesn't remove the resources associated with the project first. I'm gonna have a look how it can be solved.

[1] https://opendev.org/openstack/tempest/src/commit/77febec7848d2d031954619b6ce442c9723d0043/tempest/cmd/cleanup_service.py#L961
[2] https://opendev.org/openstack/tempest/src/commit/77febec7848d2d031954619b6ce442c9723d0043/tempest/cmd/cleanup_service.py#L988