S3 primary storage: Object not found after writing

[pierrejean-coudert]

The S3 client behaviour generates an "Object not found after writing" exception using an eventually consistent object storage provider.

It currently checks immediately for the object existence after writing. This behaviour only works with a strongly consistent read-after-write object storage provider.

[sebastiansterk]

@acsfer I'd rather say let's classify it as a bug because this leads into errors when uploading files. What do you think?

[szaimen]

Is this Issue still valid in NC21.0.2? If not, please close this issue. Thanks! :)

[sebastiansterk]

it's still valid.

[sebastiansterk]

This problem has been present for more than a year. Is there any priority for this problem? :(

[szaimen]

Hi, please update to at least 23.0.12 and report back if it fixes the issue. Thank you!

[nextcloud-command]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

[joshtrichards]

@pierrejean-coudert What underlying S3 platform/provider were you experiencing this with?

[sebastiansterk]

@pierrejean-coudert What underlying S3 platform/provider were you experiencing this with?

He uses exoscale's S3 compatible s3 storage: https://www.exoscale.com/object-storage/