The 'tempest cleanup' is not very smart, the only way how to control what's gonna be deleted is the saved_state.json file. If you wanna test what resources would be deleted, try --dry-run arg - see the doc I linked above.
As I'm thinking about it, maybe we could improve the cleanup utility so that it deletes only resources which are prefixed by "tempest" - as ~all resources created by tempest tests should be named like "tempest-<some name>-<hash>" or very similar to it.
'tempest cleanup' deletes everything it founds and is not in the saved_state.json state at the same time - see its documentation:
https:/ /docs.openstack .org/tempest/ latest/ cleanup. html
The 'tempest cleanup' is not very smart, the only way how to control what's gonna be deleted is the saved_state.json file. If you wanna test what resources would be deleted, try --dry-run arg - see the doc I linked above.
As I'm thinking about it, maybe we could improve the cleanup utility so that it deletes only resources which are prefixed by "tempest" - as ~all resources created by tempest tests should be named like "tempest-<some name>-<hash>" or very similar to it.