Migrated uploads to s3 cannot be used by Gitlab installed via Helm
Summary
Migrated uploads to s3 cannot be used by Gitlab installed via Helm.
Steps to reproduce
- Have a Gitlab installation (A) on 12.1.6 without object storage configured.
- Have a second Gitlab installation (B) using the helm chart gitlab/gitlab --version 2.6.3 which has a s3 provider configured.
- Create a backup from A and restore it in B.
- Enable object storage in A and configure the same s3 provider/buckets used in B.
- Run the raketask
gitlab:uploads:migrate:all
on A. - Visit B. You will find that all avatars are not rendering.
What is the current bug behavior?
I am using minio as s3 provider, the upload is successful, but the Gitlab installation via helm cannot read the uploaded files, as in they are rendered as missing images in the UI.
What is the expected correct behavior?
No further action should be required for the second Gitlab installation to read from the object storage.
Relevant logs and/or screenshots
Before manually re-uploading the file (broken state):
After manually re-uploading the file (working state):
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Current User: git Using RVM: no Ruby Version: 2.6.2p47 Gem Version: 3.0.3 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.0.6 Git Version: 2.22.1 Sidekiq Version:5.2.7 Go Version: unknownGitLab information Version: 12.1.6 Revision: 4016bcac51d Directory: /home/git/gitlab DB Adapter: PostgreSQL DB Version: 9.5.4 URL: https://git.company.com HTTP Clone URL: https://git.company.com/some-group/some-project.git SSH Clone URL: ssh://git@git.company.com:10022/some-group/some-project.git Using LDAP: no Using Omniauth: no
GitLab Shell Version: 9.3.0 Repository storage paths: default: /home/git/data/repositories GitLab Shell path: /home/git/gitlab-shell Git: /usr/bin/git