Bug 2135390

Summary: [rfe] improve tempest cleanup feature so that live openstack environments won't lose created data after the saved init state
Product: Red Hat OpenStack Reporter: David Hill <dhill>
Component: openstack-tempestAssignee: kstrenko
Status: CLOSED MIGRATED QA Contact: Martin Kopec <mkopec>
Severity: low Docs Contact:
Priority: low    
Version: 16.2 (Train)CC: apevec, lhh, skovili, slinaber, udesale
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-07 12:27:12 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:

Description David Hill 2022-10-17 13:40:37 UTC
Description of problem:
[rfe] improve tempest cleanup feature so that live openstack environments won't lose created data after the saved init state .   For instane, in a public cloud , if an operator runs tempest --init-saved-state while the cloud is live , it generates a snapshot of the current environment resources, but this cloud being live, new resources might be created after that command and before tempest cleanup is actually ran resulting in the loss of newly created user resources.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Martin Kopec 2022-10-18 06:08:55 UTC
There is an improvement we have been working on which would address this -> https://bugs.launchpad.net/tempest/+bug/1945082
The plan is to add another mode for cleaning the resources - the new mode would delete only resources created by tempest (those are named with "tempest-" prefix).