You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While deleting a file via direct delete or deleting its entity if S3 throws an error like a timeout, all the entries in the DB are properly deleted but the file in S3 remains.
To Reproduce
Steps to reproduce the behavior:
Start a blank state uwazi with S3 configured.
Create an entity with file or files attached
Make sure S3 service is down
Delete the file
An error is logged about S3 being down
The file does not exist in DB anymore but its in the S3 bucket.
Expected behavior
This whole process should be a transaction, if there is an error deleting the file, nothing gets deleted.
The text was updated successfully, but these errors were encountered:
Describe the bug
While deleting a file via direct delete or deleting its entity if S3 throws an error like a timeout, all the entries in the DB are properly deleted but the file in S3 remains.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
This whole process should be a transaction, if there is an error deleting the file, nothing gets deleted.
The text was updated successfully, but these errors were encountered: