Skip to content

GitLab

Closed
Created by Administrator@rootOwner

Gitolite doesn't recognize newly added SSH keys

Created by: pulse00

Since upgrading to 2.9.0 we are having troubles with ssh keys and authentication. When a SSH key is added, gitolite doesn't seem to get that information from gitlab, rejecting any push/pull operations with that key.

Here's what i found out so far:

  1. When i add a new key, that key is properly persisted in the database, with an identifier like my_mail_some_new_unique_id
  2. When cloning /home/git/repositories/gitolite-admin.git in some temporary directory, conf/gitolite.conf contains the identifier of the newly created key for the repos i have access too
  3. Also, that key is in the keydir directory

However, when i pull from that repo, i'm getting an access denied error.

What i've noticed: When i log in via ssh to the gitlab server using the git user, i'm getting a welcome message from gitlab with the identifier from my old ssh key (which i deleted prior to adding the new key).

So basically, the temporary cloned gitolite-admin repo contains the following keys after adding a new one:

  • my_mail_some_old_unique_id
  • my_mail_some_new_unique_id

However, when doing ssh [email protected], i'm getting (notice the old identifier):

hello my_mail_some_old_unique_id, this is gitolite v2.2-11-g8c4d1aa-dt running on git 1.7.9.5
the gitolite config gives you the following access:
    @R_ @W_ testing

We have restarted the server after upgrading btw.