-
Notifications
You must be signed in to change notification settings - Fork 3
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
alba_backend.presets returns wrong values #515
Comments
I've created a script to add / validate / delete a preset
It has now been running for over 5 minutes and still succeeding, so it does not seem to be an issue in the framework. |
@jeroenmaelbrancke can you please reproduce or if needed close with can't reproduce |
@jeroenmaelbrancke can we investigate if it is an integration test issue as Kevin pointed out that his side works (apperently). Maybe this is a caching problem? |
Has to be re-evaluated. There were some list-caching issue and these have been resolved in the meantime by openvstorage/framework#1991 |
One of our test scenarios is create a preset, sleep 1 second, check if this one exists and delete it again.
Sometimes the created preset is not listed when we run BackendList.get_by_name(albabackend_name).alba_backend.presets
Error from the scenario:
scenario: https://github.com/openvstorage/integrationtests/blob/master/ci/scenarios/backend/be_0002_add_update_remove_preset_test/main.py#L191
A small test on Alba create-preset, list-preset, delete-preset didn't triggered this issue. So for some reason Framework cached some stuff and do not return the correct values.
The text was updated successfully, but these errors were encountered: