actions / runner

The Runner for GitHub Actions :rocket:
https://github.com/features/actions
MIT License
4.85k stars 952 forks source link

Error: Can't use 'tar -xzf' extract archive file #1923

Closed vavuthu closed 2 years ago

vavuthu commented 2 years ago

Describe the bug

Can't use runner. getting below error while running actions

Getting action download info Download action repository 'actions/checkout@v2' (SHA:7884fcad6b5d53d10323aee724dc68d8b9096a2e) Download action repository 'actions/setup-python@v2' (SHA:7f80679172b057fc5e90d70d197929d454754a5a) Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_fcaba673-8301-4f09-b4c0-658716c016e9/0f75c0dd-581a-4910-aa5c-6a5cc9a53620.tar.gz. return code: 2.

To Reproduce Steps to reproduce the behavior:

  1. run github actions

Expected behavior

actions should be complete without any errors

Runner Version and Platform

Current runner version: '2.291.1'

OS of the machine running the runner? OSX/Windows/Linux/...

What's not working?

Current runner version: '2.291.1'
Operating System
Virtual Environment
Virtual Environment Provisioner
GITHUB_TOKEN Permissions
Secret source: None
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v2' (SHA:7884fcad6b5d53d10323aee724dc68d8b9096a2e)
Download action repository 'actions/setup-python@v2' (SHA:7f80679172b057fc5e90d70d197929d454754a5a)
Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_fcaba673-8301-4f09-b4c0-658716c016e9/0f75c0dd-581a-4910-aa5c-6a5cc9a53620.tar.gz. return code: 2.

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

igoritos22 commented 1 year ago

This issue is back, guys! All workflows have failed for me.

Peter-developer01 commented 1 year ago

The incident has been resolved. Thank you.

mx2s commented 1 year ago

I started to experience this too since about an hour ago

kevinbarabash commented 1 year ago

I've been seeing on and off starting today.

rharkor commented 1 year ago

And it's back..

Erik312 commented 1 year ago

yup its back

atticusrussell commented 1 year ago

glad to see it's not just me

Pickra commented 1 year ago

same for me

ezbeazy commented 1 year ago

ditto

sarnold commented 1 year ago

fails for me on about 30% of matrix jobs

Firefds commented 1 year ago

Experiencing this on both cloud and self-hosted Linux runners since ~15 min ago.

Incident page is now up - https://www.githubstatus.com/incidents/w01m57lwx8r3

Peter-developer01 commented 1 year ago

The incident has been resolved again. :+1:

pgupta-swi commented 1 year ago

We can see the issue started appearing again.

mmhsavolai commented 1 year ago

We're experiencing this too with many of our Linux runner actions right now.

martin-g commented 1 year ago

using actions/checkout@v4 solved the problem for me

galib120 commented 7 months ago

Pergolas DEFRA Shades Costum Outdoor Infrastructure Design & Installation More than a outdoor patio, an awning, a umbela or a veranda, pergolas with louvered roof happen to be the ultimate answer to your outdoor living satisfaction. You will need louvered pergola to: affect the amount from sunlight by partially beginning the top louvered rotor blades boostwinter temperatures through your house by pointing the baldes for the home and letting the sun’s rays in guardhome and exterior furniture by fading and deterioration enhance the value of the property.

https://defra.ae/

EagleoutIce commented 2 months ago

I again have this issue using actions/checkout@v4 - maybe because the action is located in the same repository? The issue however is flaky and only appears randomly in ~50% of the jobs per run.