On Tue, 06 Jan 2015 09:28:16 +0100 Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx> wrote: > On Mon, 2015-01-05 at 10:36 -0700, Kevin Fenzi wrote: > > > > > - Replacing an SSH key takes almost a day. > > > > That should definitely not be the case. It should take about > > > > 20-30min to sync out. > > > That's certainly not the case. I've uploaded my work key at > > > morning and 6 hours later I still cannot commit in fedora > > > repositories. > > Can you send me the exact output you get when trying to commit? > > Yesterday: > [nmavrogi@dhcp-2-127 ocserv]$ git push > Permission denied (publickey). > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > > Today: > [nmavrogi@dhcp-2-127 ocserv]$ git push > Counting objects: 4, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (4/4), done. > Writing objects: 100% (4/4), 515 bytes | 0 bytes/s, done. > Total 4 (delta 3), reused 0 (delta 0) ok. I dug into logs and found one strange issue. When you change your ssh key there should be a message emitted that it was changed, but in your case the message didn't say anything about the ssh key, it was empty. When you changed your ssh key did you do anything else in the account system interface? Or just logged in, edit account, upload new key? There's a bug here, just not sure how to isolate it. ;) kevin
Attachment:
pgpy09RFXcR2j.pgp
Description: OpenPGP digital signature
-- websites mailing list websites@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/websites
