GitLab runner fails with remote: Not Found

Hi everyone,

i have trouble to get our GitLab CI runner working on another project within the same GitLab CE instance. We have an existing repository with a .gitlab-ci.yml that works fine. On another project with almost the same settings i get the following error:

Running with gitlab-ci-multi-runner 9.3.0 (xxxxxxxx)
  on vps-67-1 (xxxxxxxx)
Using Shell executor...
Running on vps-67...
Cloning repository...
Cloning into '/root/builds/xxxxxxxx/0/project/package.name'...
remote: Not Found
fatal: repository 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.domain.com/project/package.name.git/' not found
ERROR: Job failed: exit status 1

Everything is up to date:

  • GitLab CE Version 9.2.7
  • Runner 9.3.0

I’ve setup and registered a new shared runner which also works fine for our first project. The second project will fail with exact the same issue. Both runners are registered as shared. As i’m new to this forum, please give me hint when i need to provide additional information.

Logs and also running the runner in debug mode seems not to provide additional information.

What do i need to test, where do get more information about this “remote Not Found”? Is there an option to increase log level?

Thanks a lot!
Stefan

Hi,

I see you are using the shell executor, does your second runner runs on the same machine as the first one? try to login as user gitlab-runner and clone the repo manually to check if it works.

Hope this helps.

Hi,

the second runner runs on a different virtual machine. Config works well for the first project.

How do i test this? I’ve tried to clone the repo with the https-url but not sure what CI-Token i have to use. As far as i understand this token is created temporary. I’ve used the registration token which didn’t work. A git clone (based on deploy key) works fine.

Thanks!

Hi,

First it is a good idea to always use the docker executor because it works fine on any host even if you change it.

I usually use SSH to clone repos it is easier to setup SSH keys on your second VM, however Follow this issue it might help you with this.

Hope this helps.

Hi,

thanks for your feedback. We discussed the docker executor. Our runners are located inside an OpenVZ container so far. We figured out some problems with docker container inside a OpenVZ container.

Anyway, changing the name of the repository from package.name to package-name seems to fix the issue. Can anybody confirm this?

Thanks!