Skip to content

Github website deployment failure #23549

Github website deployment failure #23549
Jan 12, 2022 · 14 answers


Hi, for some unknown reasons (or reasons I don’t understand ;)), I cannot update my webpage and got this deployment failure.
Could anyone give me an hint on how to solve this issue?
Thank you 😄

Yes, with some help! I’m not sure if your site is set up the same way, but my problem was that in the Archive step, tar was looking for gulp which was removed before it could be read.

Deleting node_modules/.bin/gulp solved it for me.

Replies

14 suggested answers

Take a look at the Actions tab of your repository. You should be able to see the logs of the build and deploy jobs there. I hope you find something useful there!

0 replies

2022-01-12T02:16:05.8788443Z Found online and idle hosted runner in the current repository’s organization account that matches the required labels: ‘ubuntu-latest’
2022-01-12T02:16:05.9999248Z Waiting for a Hosted runner in the ‘organization’ to pick this job…
2022-01-12T02:16:06.1371354Z Job is waiting for a hosted runner to come online.
2022-01-12T02:16:11.0512702Z Job is about to start running on the hosted runner: Hosted Agent (hosted)
2022-01-12T02:16:15.2180596Z Current runner version: ‘2.285.1’
2022-01-12T02:16:15.2216763Z ##[group]Operating System
2022-01-12T02:16:15.2217834Z Ubuntu
2022-01-12T02:16:15.2218432Z 20.04.3
2022-01-12T02:16:15.2218963Z LTS
2022-01-12T02:16:15.2219475Z ##[endgroup]
2022-01-12T02:16:15.2220208Z ##[group]Virtual Environment
2022-01-12T02:16:15.2220934Z Environment: ubuntu-20.04
2022-01-12T02:16:15.2221842Z Version: 20211219.1
2022-01-12T02:16:15.2222990Z Included Software: virtual-environments/Ubuntu2004-README.md at ubuntu20/20211219.1 · actions/virtual-environments · GitHub
2022-01-12T02:16:15.2224623Z Image Release: Release Ubuntu 20.04 (20211219 update) · actions/virtual-environments · GitHub

0 replies

2022-01-12T02:16:15.2225717Z ##[endgroup]
2022-01-12T02:16:15.2226408Z ##[group]Virtual Environment Provisioner
2022-01-12T02:16:15.2227165Z 1.0.0.0-main-20211214-1
2022-01-12T02:16:15.2227733Z ##[endgroup]
2022-01-12T02:16:15.2229320Z ##[group]GITHUB_TOKEN Permissions
2022-01-12T02:16:15.2230741Z Contents: read
2022-01-12T02:16:15.2231474Z Metadata: read
2022-01-12T02:16:15.2232150Z Pages: write
2022-01-12T02:16:15.2232819Z ##[endgroup]
2022-01-12T02:16:15.2236099Z Secret source: Actions
2022-01-12T02:16:15.2237302Z Prepare workflow directory
2022-01-12T02:16:15.2927391Z Prepare all required actions
2022-01-12T02:16:15.2939127Z Getting action download info
2022-01-12T02:16:15.4802719Z Download action repository ‘actions/checkout@v2’ (SHA:ec3a7ce113134d7a93b817d10a8272cb61118579)
2022-01-12T02:16:18.6187616Z ##[warning]Failed to download action ‘https://api.github.com/repos/actions/checkout/tarball/ec3a7ce113134d7a93b817d10a8272cb61118579’. Error: Response status code does not indicate success: 503 (Service Unavailable).
2022-01-12T02:16:18.6205390Z ##[warning]Back off 21.136 seconds before retry.
2022-01-12T02:16:42.8573599Z ##[warning]Failed to download action ‘https://api.github.com/repos/actions/checkout/tarball/ec3a7ce113134d7a93b817d10a8272cb61118579’. Error: Response status code does not indicate success: 503 (Service Unavailable).
2022-01-12T02:16:42.8579765Z ##[warning]Back off 20.311 seconds before retry.
2022-01-12T02:17:06.3231008Z ##[error]Response status code does not indicate success: 503 (Service Unavailable).

Here was the built log

0 replies

The end of deploy log:
2022-01-12T02:17:17.2168817Z Download action repository ‘actions/deploy-pages@v1-beta’ (SHA:e90f31fe302bdc57dfe621e71e13bcca93925130)
2022-01-12T02:17:20.3598617Z ##[warning]Failed to download action ‘https://api.github.com/repos/actions/deploy-pages/tarball/e90f31fe302bdc57dfe621e71e13bcca93925130’. Error: Response status code does not indicate success: 503 (Service Unavailable).
2022-01-12T02:17:20.3615057Z ##[warning]Back off 17.338 seconds before retry.
2022-01-12T02:17:40.8299699Z ##[warning]Failed to download action ‘https://api.github.com/repos/actions/deploy-pages/tarball/e90f31fe302bdc57dfe621e71e13bcca93925130’. Error: Response status code does not indicate success: 503 (Service Unavailable).
2022-01-12T02:17:40.8305846Z ##[warning]Back off 18.465 seconds before retry.
2022-01-12T02:18:02.4240087Z ##[error]Response status code does not indicate success: 503 (Service Unavailable).

0 replies

This is this morning attempt. It seems I cannot commit on this page anymore, at the moment.

Run actions/deploy-pages@v1-beta

Actor: github-pages[bot]

Action ID: 1688649380

Artifact URL: https://pipelines.actions.githubusercontent.com/KCoWeuWB09H8SbiB4U3D9ilxTTVHHVrFbbOuvN0Mic2bkgREQ2/_apis/pipelines/workflows/1688649380/artifacts?api-version=6.0-preview

{"count":0,"value":[]}

Failed to create deployment for be6bd76900a88238f4ff3f21ccc77ccb020cc6fd.

Error: Error: No uploaded artifact was found!

Error: Error: No uploaded artifact was found!

Sending telemetry for run id 1688649380

0 replies

Was the build job successful?

0 replies

No. It doesn’t.
It starts with
Run touch artifact.tar && tar --dereference --hard-dereference -cvf artifact.tar --exclude=.git –exclude=artifact.tar .
then a lot of lines without any issues (the photos files on the website, …etc) and finally:
Error: Process completed with exit code 1.

0 replies

Okay, you and I have the same problem. I’ll let you know if I solve it!

0 replies
sarahdijols:

2022-01-12T02:17:20.3598617Z ##[warning]Failed to download action ‘https://api.github.com/repos/actions/deploy-pages/tarball/e90f31fe302bdc57dfe621e71e13bcca93925130’. Error: Response status code does not indicate success: 503 (Service Unavailable).

That looks like a bug on the GitHub side. There was an incident around that time, maybe you got hit by that?

  <a href="https://www.githubstatus.com/incidents/cypv026dr23w" target="_blank" rel="noopener">githubstatus.com</a>

Incident with GitHub Actions and GitHub Pages

GitHub's Status Page - Incident with GitHub Actions and GitHub Pages.

0 replies

Did you manage to solve your problem? :slight_smile: 😃
I can see you deleted your own question

0 replies

Hi, Thanks for your help.
Maybe it is related, but the issue is still ongoing. I cannot build and deploy any page (I tried with a different page) this morning.

0 replies

Yes, with some help! I’m not sure if your site is set up the same way, but my problem was that in the Archive step, tar was looking for gulp which was removed before it could be read.

Deleting node_modules/.bin/gulp solved it for me.

0 replies
Answer selected

just to confirm, this is already solved, right?

0 replies

Yes, it is solved! 👍 Thanks

0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
General
Labels
None yet
4 participants