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

test_object_expiration fails with "no such file" errors after latest change to write_random_test_objects_to_bucket #9410

Closed
sagihirshfeld opened this issue Mar 3, 2024 · 0 comments · Fixed by #9411
Assignees
Labels
MCG Multi Cloud Gateway / NooBaa related issues Squad/Red

Comments

@sagihirshfeld
Copy link
Contributor

Due to a change that was introduced in #8367, the adapter util function, write_random_test_objects_to_s3_path, that was used in test_object_expiration and test_expiration_policy_filter is failing, and also no longer needed since we can just specify the prefix to write_random_test_objects_to_bucket now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MCG Multi Cloud Gateway / NooBaa related issues Squad/Red
Projects
None yet
1 participant