LFS locks inconsistency between local and remote locks

After some experimenting with LFS locks, I’m now faced with inconsistent local locks:

$ git lfs locks
Username for 'https://server': username
Password for 'https://username@server':
huge2   Sample User     ID:2

$ git lfs locks --local
huge    Another User   ID:5

As you can see, on the GitLab server, huge2 is locked by Sample User, however the local locks information only shows an obsolete lock for huge.

After calling git lfs locks I would expect to have the local information aligned.

Are my expectations wrong or is this a bug in GitLab’s LFS locking implementation?

Tested with GitLab Enterprise Edition 10.8.4-ee f80a528