Authentication failure on public LFS objects (on components)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

When running a (public) component pipeline with objects in LFS, cloning fails of the LFS objects. This should obviously not happen.

In my very simple project, I use a (public) submodule which contains an LFS tracked image. On GitLab.com we can access this asset without logging in, without problem.

When running a pipeline, jobs all fail updating the submodule (as part of the normal gitlab pre-flow, gitlab fails to update the repository with

batch response: Repository or object not found: https://gitlab-ci-token:[MASKED]@gitlab.com/ci-includes/kici.git/info/lfs/objects/batch
Check that it exists and that you have proper access to it
Failed to fetch some objects from 'https://gitlab-ci-token:[MASKED]@gitlab.com/ci-includes/kici.git/info/lfs'

This might be related that this component started to include an actual file, before LFS was enabled, but no objects where stored in LFS, which ran fine.

Reverting the png file from the LFS 'fixes' the problem.