-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Lost communication with the server due to the GitHub API returning a BadRequest or Forbidden error #3519
Comments
Hello! Thank you for filing an issue. The maintainers will triage your issue shortly. In the meantime, please take a look at the troubleshooting guide for bug reports. If this is a feature request, please review our contribution guidelines. |
Hi, im also facing similar issue here with error :- |
We have the same problem. After last step in the job, runner sends HTTP DELETE to GH API and (sometimes) gets 403 status. |
Hey everyone, are you still experiencing the problem? Maybe it was a temporary error. |
Yes, the error has persisted from the time I created this issue until today. Unfortunately, I migrated to CodeBuild a few hours ago to circumvent this problem. Therefore, it is difficult for me to provide additional information on this issue. Since many other people do not seem to be experiencing this problem, it might be an issue specific to my environment. Though it may not be relevant, let me explain my configuration: I set up a cluster on AWS EKS, used Karpenter for auto-scaling, and ran ARC runners on EC2 spot instances. Since there are no logs indicating forced termination of spot instances by AWS, it does not seem to be a problem with the spot instances. Another possible factor might be that I am using ARC for an organization that has a GitHub Enterprise Cloud contract. |
check if the runners have a sidecar or a init container. This can have side effects for the runner when it's try to communicate with github. Init containers can be setup by some operator, for example, dynatrace. :) |
Since it seems like other components that are not related to ARC are causing this issue, and the forbidden error is fixed in the latest release, I will close this issue. And please submit another issue if you find the root cause or confirm that ARC is causing this problem. |
Checks
Controller Version
0.8.3
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
The following error is displayed in the GitHub Actions execution log:
When checking the runner's pod logs, I found the following two errors:
These errors occur simultaneously in jobs running on different nodes at the same time.
Describe the expected behavior
The job completes without errors.
Additional Context
Controller Logs
Runner Pod Logs
The text was updated successfully, but these errors were encountered: