Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #23188
Closed
Open
Issue created Jul 09, 2018 by Ingo Karstein@ingo.karstein

LFS Direct_Upload not working with Minio Azure Gateway

I have Gitlab 11.0.3 running as docker image behind an nginx proxy.

I have another docker host with nginx as reverse proxy running Minio Azure Gateway.

On Windows AND Ubuntu I tried to create a GIT Repo and sync it with my GitLab Server.

On the local Repo I have "installed" Git LFS, added .gitattributes and tracked PNG files. I commited and pushed this almost empty repo to GitLab BEFORE I added a first PNG file.

I have set DIRECT_UPLOAD for LFS storage!

Executing "PUSH" faild with this error:

==> /var/log/gitlab/gitlab-workhorse/current <== 2018-07-09_06:38:46.04796 time="2018-07-09T06:38:46Z" level=error msg=error error="handleStoreLFSObject: copy body to tempfile: ETag mismatch. expected "1d66a52f517ea5469f71f9eed0aa7e2c" got "0x8D5E5669F06B013-1"" method=PUT uri=/dev/lfs-test4.git/gitlab-lfs/objects/a5804e8db7d9dd8e899333657c741c6d9081c67196ce78ef6941b01ef296895d/2218 2018-07-09_06:38:46.04801 git.example.com @ - - [2018/07/09:06:38:46 +0000] "PUT /dev/lfs-test4.git/gitlab-lfs/objects/a5804e8db7d9dd8e899333657c741c6d9081c67196ce78ef6941b01ef296895d/2218 HTTP/1.1" 500 22 "" "git-lfs/2.4.2 (GitHub; linux amd64; go 1.8.3)" 0.148

==> /var/log/gitlab/nginx/gitlab_access.log <== 172.17.0.1 - username [09/Jul/2018:06:38:46 +0000] "PUT /dev/lfs-test4.git/gitlab-lfs/objects/a5804e8db7d9dd8e899333657c741c6d9081c67196ce78ef6941b01ef296895d/2218 HTTP/1.0" 500 22 "" "git-lfs/2.4.2 (GitHub; linux amd64; go 1.8.3)"

(https://forum.gitlab.com/t/lfs-upload-not-working-to-gitlab-error-handlestorelfsobject-copy-body-to-tempfile-etag-mismatch/17332)

Some minutes ago I tried to change to BACKGROUND UPLOAD.

THIS WORKS AS EXPECTED!

I think thats a bug.

Regards Ingo

Assignee
Assign to
Time tracking