Red Hat Bugzilla – Bug 1477160
Tempest does not properly clean up resources after a failed run
Last modified: 2017-09-12 07:01:36 EDT
Created attachment 1307532 [details]
Description of problem:
Tempest cleanup --init-saved-state does not create a JSON that contains all the resources necessary, and running tempest cleanup subsequently does not remove disk/network/etc resources. The only resources cleaned up are users, groups, and flavors.
Version-Release number of selected component (if applicable):
How reproducible/Steps to Reproduce:
Run tempest --init-saved-state, then run any set of tempest tests that inlude a failure, then run tempest cleanup with the given saved state. Tempest then is unable to clean up resources that it created outside of users/projects
Tempest should cleanup the resources
Tempest does not cleanup all the resources after a failed test run
Created attachment 1307533 [details]
Created attachment 1307534 [details]
Created attachment 1307536 [details]
(In reply to Ganesh Kadam from comment #0)
> Created attachment 1307532 [details]
> tempest-ports o/p
Below is my inline comments:
> Description of problem:
> Tempest cleanup --init-saved-state does not create a JSON that contains all
> the resources necessary, and running tempest cleanup subsequently does not
> remove disk/network/etc resources. The only resources cleaned up are users,
> groups, and flavors.
[1.] Do we have trackback for the same?
As per the gived doc: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/openstack_integration_test_suite_guide/#Cleaning_Tempest_Resources
On Running tempest cleanup --init-saved-state command, It will saves the state of OpenStack deployment by saving uuid of all the resources and tenant in a saved_state.json file in the dir where command is invoked.
Once again you run 'tempest cleanup' command only it will delete the tempest resources created after that.
Please check the above doc before running it.
Created attachment 1311520 [details]
tempest.log for the reproduced steps
You can run $tempest cleanup --delete-tempest-conf-objects command to delete all left overs.
Please check this doc: https://docs.openstack.org/tempest/latest/cleanup.html