Closed seigel closed 1 month ago
Had the same issue. AFAIK the solution is to make sure that the bot is at least reader of any parent teams. For instance if you use the same team strategy as in the quick start quide, organisation.ssh.dev being your dev team. The bot needs to be in organisation.ssh.dev as a writer, but also organisation.ssh as a reader. Once you've made these changes, restart the bot with make restart
If you are able to send logs (keybase log send
) for the keybase service running on your SSH CA machine the next time this happens, that would be really helpful!
Getting this off my list.
Seems that the call to get a list of teams or something fails after a while, then never recovers, unless the bot is restarted. Is there a possibility of a connection to keybase going stal or something getting recycled in the API or the botWrapper? Can't reproduce it at will.