Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCG Scale tests might wait over or under the needed time when deleting S3 buckets #11518

Open
sagihirshfeld opened this issue Feb 27, 2025 · 0 comments
Assignees
Labels
High Priority High priority issues MCG Multi Cloud Gateway / NooBaa related issues Squad/Red

Comments

@sagihirshfeld
Copy link
Contributor

In #11511 we've noticed that we sometimes wait exactly 30 minutes between the deletion of objects from an MCG S3 bucket to the deletion of the bucket, if the scale mark was used for the test: https://github.com/red-hat-storage/ocs-ci/blob/master/ocs_ci/ocs/resources/objectbucket.py/#L489-L490

This hardcoded approach is likely to result in higher wait time than needed, and sometimes might not be enough.
We need to replace this with a dynamic solution using TimeoutSampler or retry.

@sagihirshfeld sagihirshfeld added MCG Multi Cloud Gateway / NooBaa related issues Squad/Red labels Feb 27, 2025
@udaysk23 udaysk23 added the High Priority High priority issues label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority High priority issues MCG Multi Cloud Gateway / NooBaa related issues Squad/Red
Projects
None yet
Development

No branches or pull requests

2 participants