The MigrationManager uses Shard::shouldErrorBePropagated on remote moveChunk command responses to check for errors that should not propagated back to another server. While the existing code checks the command execution errors from RemoteCommandResponse.data, it does not check any errors in sending the command, which are in RemoteCommandResponse.status. This was an oversight. All errors resulting from the remote command should be checked, sending as well as execution, before propagation back to another server.

Uncheck point: https://github.com/mongodb/mongo/commit/53efde3280dd6a880987150777f5a26143df59e1#diff-7ff1485b59b3f10b5aa430f42e785635R764