The Pagure groups are not synced with FAS till you log out and log in to pagure again. Try it and let us know if that helped.

zlopez,

Thanks. I've logged out and back in again.

https://pagure.io/group/fedora-sysadmins still shows that I'm in that group and still get:

$ git clone ssh://git@pagure.io/fedora-infra/ansible.gitCloning into 'ansible'...
git@pagure.io: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Wasn't fedora-sysadmin was a tracking group in old FAS for who was allowed to be in other sysadmin-groups? Is that kind of functionality even working in the new system or should we look at something else?

The Pagure groups are not synced with FAS till you log out and log in to pagure again. Try it and let us know if that helped.

That applies to src.fp.o but not to pagure.io whose groups are entirely
disjoint.
IIRC we had a script that could be use to sync group membership from FAS to
pagure, I think it is:
https://pagure.io/pagure-utility/blob/master/f/sync_fas_group_membership.py

In any case, I don't think the group is the problem here? Make sure the ssh key in pagure.io is the one you are using? That is not synced from fas, and you may have an old one there?

It helps when the ssh key is set correctly.

Yes, the issue was my old key was setup on pagure.io.

Cool. Glad thats working.

As to the group, we added a wide net because when we switched from internal only git for ansible, we wanted to make sure everyone who could commit before would still be able to.

That said, I think we should clean up the group. There's people who aren't active anymore and could be removed from there.
I've removed a bunch of folks. We can pare it down more as time permits.