Runner using registry image randomly gets stuck with API error (401)
Seemingly at random around 20-50% of the CI jobs on our self-hosted Gitlab CI Multi Runner get stuck.
Running in debug mode I get the following output (identifiers redacted):
WARNING: Preparation failed: API error (401): Get https://registry.gitlab.com/v2/acc/repo/manifests/image: unauthorized: HTTP Basic: Access denied
build=build project=project runner=runner
Will be retried in 3s ... build=build project=project runner=runner
Appending trace to coordinator... ok build=build build-log=0-1270 build-status=pending code=202 runner=runner sent-log=876-1270 status=202 Accepted
Feeding runners to channel builds=1
ERROR: Job failed (system failure): API error (401): Get https://registry.gitlab.com/v2/acc/repo/manifests/image: unauthorized: HTTP Basic: Access denied
build=build project=project runner=runnerThe same job will work fine if I then cancel and then retry the job.
I couldn't find any similar issues; let me know what information I can pass on to help debug this.
Thanks.
Activity
Experiencing the same issue here:
Running with gitlab-ci-multi-runner 1.11.1 (a67a225) on gitlabrunner2 Using Docker executor with image registry.gitlab.com/[redacted]/build-base:latest ... Pulling docker image registry.gitlab.com/[redacted]/build-base:latest ... Running on [redacted] via [redacted]... Cloning repository... Cloning into '/builds/[redacted]/[redacted]'... remote: HTTP Basic: Access denied fatal: Authentication failed for 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.com/[redacted]/[redacted]/'But a retry will fix it
Edited by Tomasz Maczukinmentioned in issue #2262
Please register or sign in to reply