Since upgrading to git 2.11 getting this error

[Mark Diskin]

11:33:44.714:
[ui-entities-feature] git -c core.quotepath=false push --progress --porcelain
origin
refs/heads/feature/FRWKUIE-110-remove-the-country-field-from:feature/FRWKUIE-110-remove-the-country-field-from


Counting objects: 29, done.


Delta compression using up to 8
threads.


Compressing objects: 100% (7/7),
done.


Writing objects: 100% (9/9), 698
bytes | 0 bytes/s, done.


Total 9 (delta 4), reused 0
(delta 0)


remote: Hook
ca.bitbooster.impl.PreserveFirstParentHook failed. Error: [K


remote: '/usr/bin/git rev-list
--format=%H,%P#%B%x04 --topo-order
f0347775a3c67269b62946a0bb4b4d863fe6bbe5..59489ed2881a668c726c7473da0c694cbfded8e5
^master --' exited with code 128 saying: fatal: Invalid revision range
f0347775a3c67269b62946a0bb4b4d863fe6bbe5[K


error: failed to push some refs
to 'https://vramesh@eafrmwrk.arccorp.com/git/scm/ui/ui-entities.git'


To https://vramesh@eafrmwrk.arccorp.com/git/scm/ui/ui-entities.git


!            
refs/heads/feature/FRWKUIE-110-remove-the-country-field-from:refs/heads/feature/FRWKUIE-110-remove-the-country-field-from             
[remote rejected] (pre-receive hook declined)


Done

Is it a known bug?

[G__Sylvie_Davies__bit-booster_com_]

It could be related to Bitbucket Server's own current incompatibility with Git 2.11+.  Notice this from the latest Bitbucket Server documentation:

Do NOT upgrade to Git 2.11+

Any version after Git 2.11.0 (including future 2.12+ releases) cannot be used with Bitbucket Server. Bitbucket Server 4.12 will fail on startup if Git 2.11+ is detected. Only upgrade to versions of Git which are explicitly marked supported on our Supported Platforms page.

BSERV-9388 - Pre-receive hooks and branch permissions reject valid pushes on git 2.11 

The BSERV-9388 ticket itself contains some additional information:

Bitbucket Server 4.12 will fail on startup if Git 2.11+ is detected. However, older versions of Bitbucket Server (and Stash) are not aware of the 2.11 issues (since it was released after they were), but will still be broken by them. Administrators are strongly encouraged to only upgrade to Git versions which are explicitly marked supported on ourSupported Platforms for the version of the product they're running.

I've tried to reproduce this based on what you posted, but I can't.  A few questions:

1. Does f0347775a3c67269b62946a0bb4b4d863fe6bbe5 exist on the server for that repo?
2. Does 59489ed2881a668c726c7473da0c694cbfded8e5 exist on the server for that repo?
3. For #1 and #2 you can either use web-ui (e.g. http://vm.bit-booster.com/bitbucket/projects/BB/repos/a/commits/7f103cf46fa9d30de1e24274131dfcaa09a6b179 ) or go into the repo's location on the Bitbucket server file system and type "git show <commitId>".
4. Does "master" exist on the server for that repo?
5. Are forks involved in this operation?
6. What OS (and OS version) does the Bitbucket server run on?
7. What version of Git is running on the Bitbucket server?  (Admin --> Support Tools --> System Information (tab) --> Scroll down to "Git" and look for "Version."
8. What version of Git is the client using on their workstation?
9. What version of the Bit-Booster add-on are you using?  (Admin --> Manage Add-Ons --> And then "Expand" the Bit-Booster entry to locate its version).

You said you're using git 2.11 in this question, but I'd like to know if that's client or server or both.