Commit created by Merge Request displays odd behavior after developers do a clone, pull, or fetch
This is for GitLab Community Edition 8.2.3 (Omnibus).
I have a situation where a merge request created a commit that can't be seen after users do a git pull.
From Git's perspective, the commit object is invalid, the ref has no tree, but there is no evidence of corruption in the repository after the user does a clone, pull, or fetch.
Moreover, Gitlab can still browse the commit and see the entire tree with no issues. This seems to imply that the bare repo on the Gitlab server is fine but any attempts to clone or fetch are failing to pull a valid commit object.
The following is what happens after I try to clone or fetch:
git fsck --full
(command completes with no errors)
git fsck 4b96b27394698a089ce4a0a5b0e370d41020a31c
(command completes with no errors)
git reflog show --all | grep 4b96b27394698a089ce4a0a5b0e370d41020a31c
(nothing is returned)
git rev-parse --verify 4b96b27394698a089ce4a0a5b0e370d41020a31c
(command completes with no errors)
git show 4b96b27394698a089ce4a0a5b0e370d41020a31c
fatal: bad object 4b96b27394698a089ce4a0a5b0e370d41020a31c
git log 4b96b27394698a089ce4a0a5b0e370d41020a31c
fatal: bad object 4b96b27394698a089ce4a0a5b0e370d41020a31c
git rev-list -n1 4b96b27394698a089ce4a0a5b0e370d41020a31c
fatal: bad object 4b96b27394698a089ce4a0a5b0e370d41020a31c
git branch --contains 4b96b27394698a089ce4a0a5b0e370d41020a31c
error: no such commit 4b96b27394698a089ce4a0a5b0e370d41020a31c
git checkout --detach 4b96b27394698a089ce4a0a5b0e370d41020a31c
fatal: reference is not a tree: 4b96b27394698a089ce4a0a5b0e370d41020a31c