I have a project, lets call it masterProjects/lfsTestRepo. I clone masterProjects/lfsTestRepo, run git lfs install and git lfs track *.rpm then I add the .gitattributes file, commit and push my changes.
Then I fork the repo into myProjects/lfsTestRepo. Then I clone myProjects/lfsTestRepo, add a bunch files, including some rpms, add, commit, and push my changes.
Then I go into gitlab, create a merge request from myProjects/lfsTestRepo to masterProjects/lfsTestRepo. Everything looks good in gitlab so we accept the merge request.
Now when I try to pull or re-clone masterProjects/lfsTestRepo I get a Smudge error on the first rpm file it tries to download. If I run it with git lfs install --skip-smudge then I get a [404] Object does not exist on the server or you don't ahve permissions to access it. However if I go into gitlab and navigate to the rpm files in masterProjects/lfsTestRepo I can download the rpms files just fine through the web interface.
If I fork myProjects/lfsTestRepo again, that one can be cloned just fine.
Is there something else I have to configure locally? Is there something I have to configure in gitlab? Does gitlab just not work when pushing lfs files from repos up?
Never really figured out this issue, but to resolve it we set up a new server, installed Gitlab, imported our backup and everything worked fine.
My only guess is that it had something to do with the fact that the original server had been running so long I don't think gitlab even supported LFS when we first started using it. So there must of have been something that never actually upgraded correctly but didn't throw any errors and wasn't an issue until we finally started trying to use LFS.