Hi Infra team,
Today at around 11:26 AM UTC+8 I updated my ssh key to FAS. However I cannot ssh into fedorapeople.org use the new key. After I am back with my laptop (around 21:00 UTC+8), I ssh to it and found it is still using my old key. So I temporary added the new one. So my question is, how often is the pubkey updated to fedorapeople.org?
Thanks!
On 06/22/2018 06:52 AM, Zamir SUN wrote:
Hi Infra team,
Today at around 11:26 AM UTC+8 I updated my ssh key to FAS. However I cannot ssh into fedorapeople.org use the new key. After I am back with my laptop (around 21:00 UTC+8), I ssh to it and found it is still using my old key. So I temporary added the new one. So my question is, how often is the pubkey updated to fedorapeople.org?
It is on a fedmsg driven trigger. It watches for fedmsgs that people have changed their ssh keys, figures out if the person:
* is not cla_done+1, so nothing to do. * is cla_done+1, then it updates fedorapeople and src.fedoraproject.org * is in any sysadmin group, then it updates everything.
Ah, I see the problem. I did some cleanups to the script it runs the other day and introduced a syntax error. ;(
Sorry about that, it should be back to working normally now.
kevin
On 06/23/2018 06:25 AM, Kevin Fenzi wrote:
On 06/22/2018 06:52 AM, Zamir SUN wrote:
Hi Infra team,
Today at around 11:26 AM UTC+8 I updated my ssh key to FAS. However I cannot ssh into fedorapeople.org use the new key. After I am back with my laptop (around 21:00 UTC+8), I ssh to it and found it is still using my old key. So I temporary added the new one. So my question is, how often is the pubkey updated to fedorapeople.org?
It is on a fedmsg driven trigger. It watches for fedmsgs that people have changed their ssh keys, figures out if the person:
- is not cla_done+1, so nothing to do.
- is cla_done+1, then it updates fedorapeople and src.fedoraproject.org
- is in any sysadmin group, then it updates everything.
Ah, I see the problem. I did some cleanups to the script it runs the other day and introduced a syntax error. ;(
Sorry about that, it should be back to working normally now.
Thanks for get this fixed!
kevin
infrastructure@lists.fedoraproject.org