I have a Jenkins job with "Git LFS pull after checkout" added as an additional behavior to a git repository (in MultiSCMs).
The job works properly on master executor. But on remote build node, it seems like lfs pull has no effect. There's no error message. Output is the same on both master and build node:

(...)
Checking out Revision f13e62f0215ebbe21e63ad8d4219668bdeadbeef (master)
Enabling Git LFS pull
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f13e62f0215ebbe21e63ad8d4219668bdeadbeef
 > git config --get remote.origin.url # timeout=10
using GIT_SSH to set credentials Jenkins Master
 > git lfs pull origin
Commit message: "[P12345-05729] blahblahblah"
 > git rev-parse FETCH_HEAD^\{commit} # timeout=10
(...)

But on master it works properly (large files are downloaded, I can check it by manually accessing the workspace) while on the build node it doesn't work (large files are left in "uninitialized" state, they have only a couple of bytes).
Node is accessed by master via ssh.

Edit: When I manually run `git lfs pull origin` on node's workspace (after placing the key in ~/.ssh) it properly starts to download the files. For some reason, when the same command is called by the plugin (with credentials passed using ssh key forwarding and setting GIT_SSH, I guess) it has no effect.