git clone asks for the password but I have my ~/.ssh/id_rsa.pub added
Summary
git clone
is constantly asking for git password
Steps to reproduce
- added id_rsa.pub key that is OK with github, bitbucket and ssh to account on my gitlab ce
- doing git clone - fails
Example Project
Unfortunately the server is private. The problem occurs also with deploy keys.
What is the current bug behavior?
When public key is added it fails to allow git clone
What is the expected correct behavior?
git clone ...
without asking git@
password
Relevant logs and/or screenshots
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
gitlab-rake gitlab:env:infoSystem information System: Ubuntu 16.04 Current User: git Using RVM: no Ruby Version: 2.3.6p384 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.3.0 Redis Version: 3.2.11 Git Version: 2.14.3 Sidekiq Version:5.0.5 Go Version: unknown
GitLab information Version: 10.6.4 Revision: dee2c87 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://git.teeko.io HTTP Clone URL: https://git.teeko.io/some-group/some-project.git SSH Clone URL: git@git.teeko.io:some-group/some-project.git Using LDAP: no Using Omniauth: no
GitLab Shell Version: 6.0.4 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
gitlab-rake gitlab:check SANITIZE=true Checking GitLab Shell ...GitLab Shell version >= 6.0.4 ? ... OK (6.0.4) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 5/2 ... ok 5/3 ... ok 10/5 ... ok 3/6 ... ok 3/7 ... ok 5/8 ... ok 3/9 ... ok 16/10 ... ok 18/11 ... ok 18/12 ... ok 20/13 ... ok 22/14 ... ok 22/15 ... ok 23/17 ... repository is empty 24/18 ... ok 24/19 ... repository is empty 24/20 ... repository is empty Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
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: ... 5/2 ... yes 5/3 ... yes 10/5 ... yes 3/6 ... yes 3/7 ... yes 5/8 ... yes 3/9 ... yes 16/10 ... yes 18/11 ... yes 18/12 ... yes 20/13 ... yes 22/14 ... yes 22/15 ... yes 23/17 ... yes 24/18 ... yes 24/19 ... yes 24/20 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.3.6) Git version >= 2.9.5 ? ... yes (2.14.3) Git user has default SSH configuration? ... yes Active users: ... 9
Checking GitLab ... Finished