Issue #4710 duplicate

ssh access, deployment keys sticky creating problem

yarko
created an issue

{{{

!sh

Step 1: Create a repo Step 2: Create a deployment key. Step 3: Ooops! That should have been an SSH key - delete deployment key! Step 4: Try (try!) to add that key to SSH keys ==> denied: "That key is used as a deployment key" sync, reset, reboot, wait.... repeat - cannot add that key to your SSH (w/ in 1/2 hr); give up, and generate a new key, specifically for bitbucket: Step 5: upload newly generated key; Step 6: Try (try!) to push to repo ==> $ hg push ssh://hg@bitbucket.org/yarko/clinicaltrials-svc/ pushing to ssh://hg@bitbucket.org/yarko/clinicaltrials-svc/ running ssh -C hg@bitbucket.org 'hg -R yarko/clinicaltrials-svc/ serve --stdio' remote: conq: repository access denied. deployment key is not associated with the requested repository. a bort: no suitable response from remote hg!

Step 7: check keys (locally): ssh-add -l ==> original key (used elsewhere), and new (bitbucket specific) keys present. Step 8: $ ssh-add -d $(that_first_key) ==> now it works;

}}} Ugh!

Comments (4)

  1. Log in to comment