## Summary Runner 17.5 seems to break cross project submodule authentication with job tokens. When reverting back to runner 17.4.1 it works. ``` Cloning into '/builds/example/example/git/example/example_data/example_data'... fatal: could not read Username for 'https://example.com': No such device or address fatal: clone of 'https://example.com/example/example_data/example_data.git' into submodule path '/builds/example/example/git/example/example_data/example_data' failed Failed to clone 'example_data/example_data'. Retry scheduled ``` ## Steps to reproduce Have a submodule in a project from the same gitlab domain. Allow job tokes access. -> Submodule cannot be updated on the gitlab runner 17.5 <!-- What do you need to do to reproduce the bug? Please include job definitions or git repository structure if relevant --> <!-- Please add the definition of the job from `.gitlab-ci.yml` that is failing inside of the code blocks (```) below. --> <details> <summary> .gitlab-ci.yml </summary> ```yml Add the job definition that is failing here ``` </details> ## Actual behavior Runner 17.5 cannot authenticate with job tokens to update a submodule from the same domain. ## Expected behavior Runner 17.5 can authenticate with a job token to update a submodule from the same domain. ## Relevant logs and/or screenshots <!-- Paste the job logs inside of the code blocks (```) below so it would be easier to read. --> <details> <summary> job log </summary> ```sh Add the job log ``` </details> ## Environment description We install gitlab runner from debian packages on Ubuntu 20.04 <!-- Are you using shared Runners on GitLab.com? Or is it a custom installation? Which executors are used? Please also provide the versions of related tools like `docker info` if you are using the Docker executor. --> <!-- Please add the contents of `config.toml` inside of the code blocks (```) below, remember to remove any secret tokens! --> <details> <summary> config.toml contents </summary> ```toml Add your configuration here ``` </details> ### Used GitLab Runner version <!-- Please run and paste the output of `gitlab-runner --version`. If you are using a Runner where you don't have access to, please paste at least the first lines the from build log, like: ``` Running with gitlab-ci-multi-runner 1.4.2 (bcc1794) Using Docker executor with image golang:1.8 ... ``` --> ## Possible fixes Revert back to gitlab runner 17.4.1.