-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Minio v6 -> v7 breaks for Ceph due to ListObjectsV2 #3291
Comments
As for any practical suggestions - maybe add a "UseV1 = true" config key in the AWS bucket config file? I can work on that PR if it sounds reasonable. |
We're also running on Ceph and are affected by this. I like the idea to have a bucket config option to revert to V1 of the ListObjects API in the interim, while we upgrade our Ceph installs. |
2 tasks
I made a PR for this. |
The PR has been merged so closing this! Thank you for this fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. When upgrading from Thanos 0.14.0 to 0.16.0-rc.0 (and 0.15.0 should have the same issue), this breaks with Ceph.
This is due to the minio client upgrade from v6 to v7: https://github.com/thanos-io/thanos/pull/2970/files
This breaks for me because the version of Ceph we operate has trouble with the ListObjectsV2 operation (if you look this up it's a known issue for minio/Ceph) - e.g. minio/minio-go#1130
I can hotfix my own local clone of Thanos to add this:
Maybe Ceph users are a small population that this doesn't matter.
The text was updated successfully, but these errors were encountered: