I think this is in fact the same error as: https://pagure.io/fedora-infrastructure/issue/9012 but when I tried I was not able to reproduce it :(

I'm not seeing any deploy key in https://pagure.io/fedora-docs-l10n/fedora/settings#deploykey-tab
So maybe it's not the same error.

@misc do you need some help to debug this?

I just deleted it and tried to added it again, and it now fails, so there is no ssh key anymore on the weblatebot user :/

@misc said we probably need to have a look in sundries01.iad2.fedoraproject.org for the file ~_update_docs_trans/.ssh/id_rsa_docs_trans.pub

Ok so I propose that:
https://pagure.io/fedora-infra/ansible/pull-request/136

This would display the key, then I could just run the playbook and give the key to jibec without needing a admin with more access than me. In a ideal world, I should be able to push the pub key directly but I guess that's more complicated.

I will merge tomorrow if no one is against the idea.

Did https://pagure.io/fedora-infra/ansible/pull-request/136 fixed this?

Anything else we need to figure out?

I need to be able to run the script:

[misc@bastion01 ~][PROD-IAD2]$ sudo rbac-playbook groups/sundries.yml 
Password+Token: 
misc is not in the sudoers file.  This incident will be reported.

Did the process changed (as I checked the doc, but it might not have been updated) ?

I need to be able to run the script:
[misc@bastion01 ~][PROD-IAD2]$ sudo rbac-playbook groups/sundries.yml

^^^^
You want batcave01 there... not bastion01...

Password+Token:
misc is not in the sudoers file. This incident will be reported.

Did the process changed (as I checked the doc, but it might not have been updated) ?

Nope, should be the same, just use batcave01. ;)

Yup, I just found by myself after a while. Monday :(

I sent the key to jibec by mail, so closing. I should have also created a ed25259 rather than RSA, but well.