-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Storage in S3 buckets using minio not working in Gitea 1.20.0 with working config from Gitea 1.19.4 #25984
Comments
I have updated to Gitea 1.20.1 (Now using Gitea chart 9.0.4). If I configure MINIO_LOCATION to the location of my existong bucket, it sounds like minio tries to create the bucket??
|
What's your workround? Maybe I can get some clues to fix it. |
I have no workaround? I can no longer use my S3 storage. It's just that the error i the log changes if I set MINIO_LOCATION. I assume my problem is related to Rework storage settings -> #23911 But since I only have one section with storage config, I think my config should still work. I have a hard time following the changes being described in #23911 |
Yes, I think so. Can you post your generated storage configuration in app.ini and remove the seurity informations. And I will figure it out tomorrow. |
Here is my app.ini. I have had to set storage.STORAGE_TYPE = local to get the pod to start up. The rest of the config in [storage] is untouched. I don't know if I should configure storage.MINIO_LOCATION or not? The error changes when I do (As described in earlier posts):
|
I'm assuming this is related, but since the update my For the time being I just set up a symbolic link. My redacted configuration:
|
Any idea as to what could be causing this issue? Is it a problem in Minio? |
On v1.20.2 the error still appears. |
…st and then create one if it doesn't exist (#26420) For some reason, the permission of the client_id and secret may cannot create bucket, so now we will check whether bucket does exist first and then try to create a bucket if it doesn't exist. Try to fix #25984 Co-authored-by: silverwind <me@silverwind.io>
…st and then create one if it doesn't exist (go-gitea#26420) For some reason, the permission of the client_id and secret may cannot create bucket, so now we will check whether bucket does exist first and then try to create a bucket if it doesn't exist. Try to fix go-gitea#25984 Co-authored-by: silverwind <me@silverwind.io>
#26465) Backport #26420 by @lunny For some reason, the permission of the client_id and secret may cannot create bucket, so now we will check whether bucket does exist first and then try to create a bucket if it doesn't exist. Try to fix #25984 Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: silverwind <me@silverwind.io>
Description
Storage in s3 buckets (using minio) no longer works when using Gitea 1.20.0 with chart v9.0.0. Changing the Gitea version to 1.19.4 with chart v9.0.0 (same configuration) makes storage in s3 buckets work again as described in the issue here:
https://gitea.com/gitea/helm-chart/issues/469
The storage configuration is:
With the above storage config, Gitea 1.20.0 says:
Is Gitea/minio trying to create the existing bucket?
Gitea Version
1.20.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
In Kubernetes with chart v9.0.0.
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: