#9833 fedpkg clone fails with Permission denied (publickey)
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by crvi.

Describe what you would like us to do:


$ fedpkg clone gnome-activity-journal

fails

Cloning into 'gnome-activity-journal'...
crvi@pkgs.fedoraproject.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.

I have uploaded my ssh rsa public key to https://accounts.fedoraproject.org/user/crvi/settings/keys/. It has been more than 12 hours.

When do you need this to be done by? (YYYY/MM/DD)


As quick as possible.


Confusingly, Only folks in the 'packager' group can use ssh on src.fedoraproject.org/pkgs.fedoraproject.org. ;(

You will need to use https instead:

See https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits

Basically you want to use fedpkg -a

Hope that helps!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

I am part of "Fedora Packager GIT Commit Group".

Metadata Update from @crvi:
- Issue status updated to: Open (was: Closed)

3 years ago

ok. Sorry about that, was looking at old data. ;(

Anyhow, it's not accepting your key.

  • Can you try and login to fedorapeople.org ? Does that work?

  • Does ssh-add -L show your key in your local agent?

Can you try and login to fedorapeople.org ? Does that work?

Yes

Does ssh-add -L show your key in your local agent?

Yes

When you sshk crvi@pkgs.fedoraproject.org -vvv do you see anything special?

ok. We found the problem and it should be fixed now. :)

The underlying cause is still not clear to me, but I think we will see wait and see if it happens again. It may have been related to reboots or the like.

If you still see problems, please do reopen this, but it should be working now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago
$ ssh crvi@pkgs.fedoraproject.org
crvi@pkgs.fedoraproject.org: Permission denied (publickey).
[test@rawhide tmp]$ fedpkg clone gnome-activity-journal
Cloning into 'gnome-activity-journal'...
crvi@pkgs.fedoraproject.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
$ ssh crvi@fedorapeople.org

Last login: Sat Apr  3 20:18:38 2021 from 122.179.62.220
================================== ATTENTION ==================================

        This is a PRIVATE computer system, unauthorized access is
        strictly prohibited.

This system is to be used for Fedora Project and related purposes only.  This
is not your personal computing system.  Users who are unsure whether or not
they have access to this system, don't have it and should log off immediately.

There is no expectation of privacy of any kind on this system.  All questions
concerning access should be directed to admin@fedoraproject.org

===============================================================================

This system is ansible managed!  Local changes may be overwritten.

Security Category: Low
Primary Contact: Fedora admins - admin@fedoraproject.org
Environment: production
Freezes: False
Purpose: Provide hosting space for Fedora contributors and Fedora Planet
Relationship: - shell accounts and web space for fedora contributors
- web space for personal yum repos
- shared space for small group/personal git repos

 Please be aware that this is a shared server, and you should not upload
 Private/Secret SSH or GPG keys onto this system. Any such keys found
 will be deleted.

This document is provided as part of CSI standards.  
See https://infrastructure.fedoraproject.org/csi/security-policy/ for more information. 
[crvi@people02 ~][PROD]$ 

Metadata Update from @crvi:
- Issue status updated to: Open (was: Closed)

3 years ago

Oops. One thing wasn't pushed yet.

Can you try again now?

Works now.

Thanks Kevin.

Also, how long does it take for new ssh public keys to take effect ?

It should be pretty instant. There's a sssd cache I think of 2 minutes...

Sorry for all the trouble.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata