Bug 1763050
| Summary: | tempest cleanup command is not cleaning up regions | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Michele Valsecchi <mvalsecc> | ||||
| Component: | openstack-tempest | Assignee: | Lukas Piwowarski <lpiwowar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Kopec <mkopec> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 13.0 (Queens) | CC: | apevec, chkumar, dhill, lhh, lpiwowar, mvalsecc, slinaber, udesale | ||||
| Target Milestone: | z11 | Keywords: | Triaged, ZStream | ||||
| Target Release: | 13.0 (Queens) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-tempest-18.0.0-12.el7ost | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1787368 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-03-10 11:52:51 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1787368 | ||||||
| Attachments: |
|
||||||
Created attachment 1662398 [details]
verification output
The 'Fixed in version' contains the fix for the issue, verified on a 13 env using 2020-02-06.2 puddle. Verification output attached.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0769 |
Description of problem: `tempest cleanup` command is not cleaning up the region(s) tempest has creates during its execution. Running `tempest run --smoke` (even followed by `tempest cleanup`) a few times, will results in many unused regions being created and left behind. Version-Release number of selected component (if applicable): 13.0.7 13.0.8 (Haven't tested version lower than 13.0.7) How reproducible: $ openstack region list +-----------+---------------+-------------+ | Region | Parent Region | Description | +-----------+---------------+-------------+ | regionOne | None | | +-----------+---------------+-------------+ $ tempest cleanup --init-saved-state $ ll saved_state.json -rw-rw-r--. 1 stack stack 107598 Oct 18 02:32 saved_state.json <=== state is saved $ tempest run --smoke $ tempest cleanup --dry-run Begin cleanup Process 0 projects $ cat dry_run.json { "_projects_to_clean": {}, "domains": [], "flavors": [], "images": [], "projects": [], "roles": [], "users": [] } $ openstack region list +---------------------------+---------------+-------------+ | Region | Parent Region | Description | +---------------------------+---------------+-------------+ | regionOne | None | | | tempest-region-1060190437 | None | | <===== | tempest-region-259179736 | None | | <===== regions are left behind, after cleaning up (--dry-run): this is expected | tempest-region-303446827 | None | | <===== | tempest-region-945563805 | None | | <===== +---------------------------+---------------+-------------+ $ tempest cleanup Begin cleanup Process 0 projects $ openstack region list +---------------------------+---------------+-------------+ | Region | Parent Region | Description | +---------------------------+---------------+-------------+ | regionOne | None | | | tempest-region-1060190437 | None | | <===== | tempest-region-259179736 | None | | <===== regions are left behind, after cleaning up: this is not expected | tempest-region-303446827 | None | | <===== | tempest-region-945563805 | None | | <===== +---------------------------+---------------+-------------+ Actual results: `tempest cleanup` should restore the environment to the same state where it was before running `tempest run`. Expected results: `tempest cleanup` leaves behind regions it created during its execution