Skip to content

GitLab

Closed
Created by Administrator@rootOwner

Creating a new repo creates two user_ids and SSH keys?!

Created by: tr37ion

I create an new project with Gitlab 3.1. Then I want to push my git repo to the new Gitlab repo via:

`git push -u origin master`

then I get the following CLI error message:

W access for flux DENIED to gituser_domain_com_1356458002
(Or there may be no repository at the given path. Did you spell it correctly?)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.

If I look at the /home/git/.gitolite/keydir/ folder I can find TWO SSH keys for the same user! One with the wrong ID:

gituser_domain_com_1356458002.pub
gituser_domain_com_1363261048.pub

Also in the /home/git/.gitolite/conf/gitolite.conf the new Gitlab repo has the wrong user_id:

repo    gitolite-admin
  RW+                            = gitlab
repo    test
  RW+                            = @all
repo    @all
  RW+                            = gitlab
repo    flux
  RW+                            = gituser_domain_com_1363261048
  config core.sharedRepository = 0660

Moreover the /home/git/.gitolite/conf/gitolite.conf-compiled.pm is also using the wrong user-id for the new project. /home/git/.ssh/authorized_keys shows the same misconfiguration.

command="/home/git/bin/gl-auth-command gitlab",no-port-forwarding,no-X11- forwarding,no-agent-forwarding,no-pty ssh-rsa AAAAB3Nn0nKeY
command="/home/git/bin/gl-auth-command gituser_domain_com_1356458002",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty
command="/home/git/bin/gl-auth-command gituser_domain_com_1363261048",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty
command="/home/git/bin/gl-auth-command gituser_domain_com_1356458002",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty
command="/home/git/bin/gl-auth-command gituser_domain_com_1356624072",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty

It seems Gitlab is still using an 'old' user_id, which wasn't removed properly.

How can I delete the obsolete user and let me push my repo with the right user_id?