-
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
Set *:object_store:enabled
in gitlab.yml regardless the value
#2579
Set *:object_store:enabled
in gitlab.yml regardless the value
#2579
Conversation
c6a4ab1
to
21af33f
Compare
upload:object_store:enabled
in gitlab.yml even if "false"*:object_store:enabled
in gitlab.yml regardless the value
I have started the PR only fixing uploads section, but found that can be applied to artifacts, lfs, packages, terraform_state. The log message above shows that the error is happen when initializing lfs:object_store. |
21af33f
to
ea0b504
Compare
ea0b504
to
a70c041
Compare
apply for artifact,packages,terraform_state,lfs,uploads
a70c041
to
844d57d
Compare
@sachilles Sure it can be applied for 14.x series I think. Use my commit freely if you need to do that. Then, we'd better to check assignment for whole environment variables. Let's have a discussion at #2594 |
Ah sorry for meaningless response above, I misunderstood something. I have checked #2594 but there were no duplication or conflict. The PR #2594 is about to change default value when the environment variable is not set. I think the PR #2438 author just forgot to change it when copying and modifying the various settings in |
Hi @kkimurak, PR #2594 changes the value of the variable even if the variable is set. The result is an overlapping of bucket storage, data that is supposed to go on the terraform state bucket would end up on the packages one. |
Oh sorry. I was completely misunderstood something. You are about to correct assignment of environment value itself, not default value. @Syphon83 Thank you for correcting me. Anyway, there are no concurrent work. we can merge both with no issues, I think. |
@kkimurak Don't worry, it was my frustration speaking. I was SO close to make a mess with data inside buckets. @sachilles Do you agree? Thank you. |
In current code,
upload:object_store:enabled
is updated only ifGITLAB_UPLOADS_OBJECT_STORE_ENABLED
is set totrue
. It makespuma
to die because of invalid value appears to configuration.This can be fixed by running
update_template GITLAB_UPLOADS_OBJECT_STORE_ENABLED
regardless of the value.Here is a
/var/log/gitlab/supervisor/puma.log
that shows puma reporting exception./var/log/gitlab/supervisor/puma.log