Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CircleCI workflows are broken due to missing permission #7067

Closed
pmeier opened this issue Jan 9, 2023 · 4 comments
Closed

CircleCI workflows are broken due to missing permission #7067

pmeier opened this issue Jan 9, 2023 · 4 comments

Comments

@pmeier
Copy link
Contributor

pmeier commented Jan 9, 2023

Currently, no CircleCI job is able to run. They fail with

Using SSH Config Dir '/home/circleci/.ssh'
git version 2.38.2
Cloning git repository
Cloning into '.'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

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

exit status 128

For example: https://app.circleci.com/pipelines/github/pytorch/vision/22512/workflows/5383f39a-13e8-4b22-a869-a2faa8e3e66a/jobs/1804282

This is most likely related to rotating our secrets in response to https://circleci.com/blog/january-4-2023-security-alert/.

cc @seemethere @malfet @atalman

@vmoens
Copy link
Contributor

vmoens commented Jan 9, 2023

Had the same problem with RL
Here's what I did:
Go to circleci settings and deactive the ssh key:

Project settings > SSH Keys > Deploy Key
Deactivate it by clicking on the right cross.

Then from our meta OSS tool, re-activate circleci which should be deactivated.

Worked for me, hoping it does for you

cc @NicolasHug

@NicolasHug
Copy link
Member

Thanks for the tips @vmoens

@pmeier I just completed the steps above and re-triggered #5009. Let's see if it works

@NicolasHug
Copy link
Member

Looks like it worked: https://app.circleci.com/pipelines/github/pytorch/vision/22514/workflows/2f117247-9236-4be3-a950-546c202d0bfd/jobs/1804317

(this one is red but at least it's running).

Good to close @pmeier ?

@pmeier
Copy link
Contributor Author

pmeier commented Jan 9, 2023

Yeah, the failure is related to #7060. So yes, I think we are good. Thanks @vmoens for the instructions and @NicolasHug for acting on them!

@pmeier pmeier closed this as completed Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants