Add scripts to simplify Tempest testing #1360
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jackhodgkiss
reviewed
Nov 4, 2024
Alex-Welsh
force-pushed
the
tempest-scripts
branch
from
cf5f56e to
f4fa9de
Compare
Alex-Welsh
added
enhancement
|
Found a couple of issues in testing, converting to draft for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added two scripts:
run-tempest.shmakes it easy to run Tempest teststempest-cleanup.shdoes a reasonable job of clearing up openstack resources that have been left behind by Tempest failures. It is not perfect but something is better than nothing and we can iterate on it over time.They've been hanging around on a few client deployments I've used so I'm adding them here for all to enjoy.