Chapter 6. Cleaning Tempest Resources

After running tempest, there will be files, users and tenants created in the testing process that need to be deleted. Being able to self clean is one of the design principles of tempest.

6.1. Performing a Clean Up

First you must initialize the saved state. This creates the file saved_state.json, which prevents the cleanup from deleting objects that need to be kept. Typically you would run cleanup with --init-saved-state prior to a tempest run. If this is not the case, saved_state.json must be edited to remove objects you want cleanup to delete.

# tempest cleanup --init-saved-state

Run the cleanup:

# tempest cleanup

6.2. Performing a Dry Run

A dry run lists the files that would be deleted by a cleanup, but does not delete any files. The files are listed in the dry_run.json file.

# tempest cleanup --dry-run

6.3. Deleting Tempest Objects

Delete users and tenants created by tempest:

# tempest cleanup --delete-tempest-conf-objects