fatal: Couldn't find remote ref refs/pipelines/12059
Summary
Sometimes when the CI is bulding the job failes with error:
Pulling docker image docker:dind ...
Using docker image sha256:eaed9efc02d231a28b0f7725551a71459a7763e83bcda5464db66ec4684a1639 for docker:dind ...
Running on runner-51e4e52b-project-20-concurrent-0 via runner-51e4e52b-RUNNER-1573545843-de9617ee...
Fetching changes...
Initialized empty Git repository in /builds/WMSE/multi-website-system/.git/
Created fresh repository.
fatal: Couldn't find remote ref refs/pipelines/12059
ERROR: Job failed: exit code 1
Steps to reproduce
- Every action of the the CI runner. Example when building a image. It doen'St happen everytime but it happens often.
What is the current bug behavior?
(What actually happens)
What is the expected correct behavior?
No git fatal error
Relevant logs and/or screenshots
Results of GitLab environment info
- Self Hosted
- Gitlab Community Edition
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
System information
System: Ubuntu 18.04
Current User: git
Using RVM: no
Ruby Version: 2.6.3p62
Gem Version: 2.7.9
Bundler Version:1.17.3
Rake Version: 12.3.3
Redis Version: 3.2.12
Git Version: 2.22.0
Sidekiq Version:5.2.7
Go Version: go1.10.4 linux/amd64
GitLab information
Version: 12.4.2
Revision: 393a5bdafa2
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 10.9
URL: https://gitlab.basecom.de
HTTP Clone URL: https://gitlab.basecom.de/some-group/some-project.git
SSH Clone URL: git@gitlab.basecom.de:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: crowd
GitLab Shell
Version: 10.2.0
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
Git: /opt/gitlab/embedded/bin/git
</pre>
</details>
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 10.2.0 ? ... OK (10.2.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab App ... Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 4/1 ... yes 10/6 ... yes 12/8 ... yes 17/11 ... yes 17/12 ... yes 17/13 ... yes 17/14 ... yes 17/15 ... yes 17/16 ... yes 17/17 ... yes 17/18 ... yes 17/19 ... yes 21/20 ... yes 17/21 ... yes 17/22 ... yes 17/23 ... yes 17/24 ... yes 21/25 ... yes 17/26 ... yes 34/29 ... yes 37/30 ... yes 44/32 ... yes 17/33 ... yes 17/37 ... yes 17/38 ... yes 17/39 ... yes 48/41 ... yes 48/42 ... yes 37/43 ... yes 17/44 ... yes 44/45 ... yes 56/48 ... yes 56/51 ... yes 59/52 ... yes 17/54 ... yes 17/55 ... yes 61/56 ... yes 59/57 ... yes 59/58 ... yes 59/59 ... yes 59/60 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.3) Git version >= 2.22.0 ? ... yes (2.22.0) Git user has default SSH configuration? ... yes Active users: ... 38 Is authorized keys file accessible? ... yes Checking GitLab App ... Finished Checking GitLab subtasks ... Finished
Edited by 🤖 GitLab Bot 🤖

