Open jeroenmaelbrancke opened 6 years ago
I've created a script to add / validate / delete a preset
while True:
AlbaPresetController.add_preset(alba_backend.guid, name='test', compression='snappy', policies=[[2,2,3,4]], encryption='aes-cbc-256')
print 'Preset added'
if not any(pr['name'] for pr in alba_backend.presets if pr['name'] == 'test'):
break
print 'Preset present'
AlbaPresetController.delete_preset(alba_backend.guid, name='test')
print 'Preset removed'
if any(pr['name'] for pr in alba_backend.presets if pr['name'] == 'test'):
print 'Preset still present, while it should have been removed'
break
print ''
It has now been running for over 5 minutes and still succeeding, so it does not seem to be an issue in the framework. Please provide us with more information or investigate this issue further in the integrationtests first
@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 https://github.com/openvstorage/framework/issues/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.