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

Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/ee0669bd1cc54295c223e0bb666b733df41de1c5'. Error: Response status code does not indicate success: 503 (Service Unavailable) #1457

Closed
copyNdpaste opened this issue Sep 5, 2023 · 8 comments

Comments

@copyNdpaste
Copy link

v3, v2 not work

Current runner version: '2.308.0'
Runner name: 'ecs-ec-backend-runner-dev'
Runner group name: 'Default'

GITHUB_TOKEN Permissions
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v2' ()
Warning: Failed to download action 'https://api.github.com/repos/actions/checkout/tarball/ee0669bd1cc54295c223e0bb666b733df41de1c5'. Error: Response status code does not indicate success: 503 (Service Unavailable).
@leepowellnbs
Copy link

Getting the same on actions/checkout@v3

@copyNdpaste
Copy link
Author

action works now.....

@RMEngels
Copy link

RMEngels commented Sep 5, 2023

Seems to be unrelated to version, v4 also fails here

@Lyokolux
Copy link

Lyokolux commented Sep 5, 2023

It seems to fail from time to time. As the checkout didn't change and it works partially, maybe something is going on by Github.

@Lyokolux
Copy link

Lyokolux commented Sep 5, 2023

It seems to be a duplicate of #1456, and an incident by Github https://www.githubstatus.com/history

@thboop
Copy link
Contributor

thboop commented Sep 5, 2023

Hey folks, we are aware of this issue. The incident should be resolved now but please let us know if you see it again.

@thboop thboop closed this as completed Sep 5, 2023
@slavik-pastushenko
Copy link

Hey folks, we are aware of this issue. The incident should be resolved now but please let us know if you see it again.

@thboop Hey Thomas! Seems like an issue is still in place, for both v3 & v4.

@tepatelcmc
Copy link

Hi
I am still experiencing this issue and it seems to be a blocker. Any other workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants