HDDS-5272. Make ozonefs.robot execution repeatable #2280
Merged
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.
What changes were proposed in this pull request?
Most of our smoketests can be executed multiple times, which helps us to debug the tests locally.
Unfortunately, it's not the case
ozonefs/ozonefs.robot. This test uses hard-coded bucket/volume names instead of using randomized bucket names.For example:
docker-compose up -d --scale datanode=3
docker-compose exec scm bash
robot smoketest/ozonefs/ozonefs.robot
robot smoketest/ozonefs/ozonefs.robot
The second execution fails which makes harder to debug test problems.
It seems to be better to follow existing pattern and adding a random prefix to the user bucket names.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5272
How was this patch tested?