v7.10.3 / 1.75.1 lost/erased all files from S3
-
I had something similar happen at a different S3 provider, and after 2 months, the solution was to delete that bucket and create a new one, as their infrastructure has upgraded past the support for the original bucket code version, heh.
-
I had something similar happen at a different S3 provider, and after 2 months, the solution was to delete that bucket and create a new one, as their infrastructure has upgraded past the support for the original bucket code version, heh.
-
@robi wtf
?!
Could possibly share the providers names? And how on earth could it be that s3 content can get lost because of the version’s update?!@potemkin_ai nah, too much drama
-
@potemkin_ai nah, too much drama
-
-
@potemkin_ai nope just regular backups
@robi who cares about backups, right?
I would appreciate though if you could share (here or any other way) the providers names; not a problem if not, but I would feel better knowing what to avoid. -
In my specific case, Exoscale's support was quite helpful - they checked the logs of the script that calculates the bucket size and they pointed out that the bucket was always empty.
After additional checks, I realized that Mattermost doesn't respect file's storage settings and doesn't upload files to s3, even if S3 connection works; I believe something goes wrong with using those settings which leads Mattermost to silently default to work with local storage. I understand it shall be reported upstream, but I have no capacity for that right now, so just leaving this note here for now - in case if someone will encounter this issue as well.
-
@scooke yes, the files were stored locally all of the time, despite my settings were quite opposite (S3)
