此内容没有您所选择的语言版本。

Chapter 7. Cleaning Tempest Resources


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

7.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 that you want cleanup to delete.

# tempest cleanup --init-saved-state
Copy to Clipboard Toggle word wrap

Run the cleanup:

# tempest cleanup
Copy to Clipboard Toggle word wrap

The tempest cleanup command deletes tempest resources but does not delete projects or the tempest administrator account.

7.2. Performing a Dry Run

It is recommended to perform a dry run before executing the real cleanup. 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. Check the dry_run.json file to ensure that the cleanup does not delete any files that you require for your environment.

# tempest cleanup --dry-run
Copy to Clipboard Toggle word wrap

7.3. Deleting Tempest Objects

Run the following command to delete all tempest resources, including projects, but not the tempest administrator account:

# tempest cleanup --delete-tempest-conf-objects
Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2026 Red Hat
返回顶部