actions/deploy-pages v2 failing with HttpError: Invalid artifact url #225

matthewfeickert · 2023-09-22T14:43:29Z

Hi. I have a GitHub Pages deployement workflow (at https://github.com/matthewfeickert/chep-2023-proceedings-software-citation) that worked 5 hours ago and now with no changes to the GitHub Actions workflow

...

# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions:
  contents: read
  pages: write
  id-token: write

...

jobs:

...

  deploy:
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    runs-on: ubuntu-latest
    needs: [build]

    steps:
    - name: Setup Pages
      uses: actions/configure-pages@v3

...

    - name: Upload artifact
      uses: actions/upload-pages-artifact@v2

    - name: Deploy to GitHub Pages
      id: deployment
      uses: actions/deploy-pages@v2

actions/upload-pages-artifact@v2 is succeeding (as expected)

With the provided path, there will be 1 file uploaded
Starting artifact upload
For more detailed logs during the artifact upload process, enable step-debugging: https://docs.github.com/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging
Artifact name is valid!
Container for artifact "github-pages" successfully created. Starting upload of file(s)
Total size of all the files uploaded is 91038 bytes
File upload process has finished. Finalizing the artifact upload
Artifact has been finalized. All files have been successfully uploaded!

The raw size of all the files that were specified for upload is 102400 bytes
The size of all the files that were uploaded is 91038 bytes. This takes into account any gzip compression used to reduce the upload size, time and storage

Note: The size of downloaded zips can differ significantly from the reported size. For more information see: https://github.com/actions/upload-artifact#zipped-artifact-downloads 

Artifact github-pages has been successfully uploaded!

but then actions/deploy-pages@v2 is failing with

Artifact exchange URL: https://pipelinesghubeus7.actions.githubusercontent.com/MRRFg7wazEjuUfP6wl9C860DSXHdL0R9UvtunX1JdvJ7cAPJoH/_apis/pipelines/workflows/6275317421/artifacts?api-version=6.0-preview
Creating Pages deployment with payload:
{
	"artifact_url": "https://pipelinesghubeus7.actions.githubusercontent.com/MRRFg7wazEjuUfP6wl9C860DSXHdL0R9UvtunX1JdvJ7cAPJoH/_apis/pipelines/1/runs/6/artifacts?artifactName=github-pages&%24expand=SignedContent",
	"pages_build_version": "342dcb9c508e0f873196d0c332e98c7ac6852dfd",
	"oidc_token": "***"
}
Error: Creating Pages deployment failed
Error: HttpError: Invalid artifact url
    at /home/runner/work/_actions/actions/deploy-pages/v2/webpack:/deploy-pages/node_modules/@octokit/request/dist-node/index.js:86:1
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v2/webpack:/deploy-pages/src/internal/api-client.js:126:1)
    at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v2/webpack:/deploy-pages/src/internal/deployment.js:80:1)
    at main (/home/runner/work/_actions/actions/deploy-pages/v2/webpack:/deploy-pages/src/index.js:30:1)
Error: Error: Failed to create deployment (status: 400) with build version 342dcb9c508e0f873196d0c332e98c7ac6852dfd. Responded with: Invalid artifact url

https://www.githubstatus.com/ is also not currently showing any degraded performance.

Does anyone know what broke?

The text was updated successfully, but these errors were encountered:

jameschensmith · 2023-09-22T14:48:23Z

I'm experiencing this issue as well. Not sure if this helps, but I noticed the base URL has changed:

Successful pipeline: https://pipelines.actions.githubusercontent.com
Failed pipeline: https://pipelinesghubeus7.actions.githubusercontent.com

GlobalMin · 2023-09-22T15:02:02Z

Experiencing as well and linking to large thread where we have 20 or so confirmations and growing.

https://github.com/orgs/community/discussions/67961

Bluefissure · 2023-09-22T15:07:02Z

I think it is a server-side issue, I checked the log of previous successful runs and github was returning the https://pipelines.actions.githubusercontent.com as artifact raw url. Starting earlier today the returned url was changed to the mirror sites, which causes it to be invalid.

viac92 · 2023-09-22T15:13:12Z

The last successful deployment of my website was 1 hour ago 16pm CEST, after that I tried few minutes later but every attempts failed.

rtvkiz · 2023-09-22T15:21:53Z

Facing same issue, not able to deploy anything to github pages, the artifact url states:

"typeName": "Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server",
    "typeKey": "UnauthorizedRequestException"

GlobalMin · 2023-09-22T15:33:33Z

@JamesMGreene looks like you maintain this repo

ghkdqhrbals · 2023-09-22T15:34:41Z

There appears to be a permissions issue with the new request URL https://pipelinesghebeus7.actions.githubusercontent.com.

When I checked the URL above, it said The user 'System:PublicAccess;aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' is not Authorized. From my point of view, System:PublicAccess;aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa is not a common view. So, this access ID has been merged incorrectly.

dgarcu · 2023-09-22T15:39:57Z

I have experienced problems too. I have also commented on the mentioned thread.

kstiehl · 2023-09-22T15:42:32Z

We have the same issue here

v8-j · 2023-09-22T15:43:07Z

And me

akoroliova · 2023-09-22T15:50:40Z

Upvoting, hope this is fixed soon

jonjoncardoso · 2023-09-22T15:52:23Z

Same problem here!

dahmani-karim · 2023-09-22T15:57:45Z

Hi ! Same error in my workflow, invalid artifact url errors stop the publish action

ChrisHammond · 2023-09-22T16:01:43Z

+1

mlettini · 2023-09-22T16:16:00Z

Same

Ew4n1011 · 2023-09-22T16:17:49Z

Upvoting, same error on my workflow, hopefully fixed soon

tomfrancis-2211 · 2023-09-22T16:19:25Z

same error is it looking like a server problem?

JamesMGreene · 2023-09-22T16:21:08Z

I'll start investigating. Guessing an upstream change rolled out today. 😓
Thanks for raising our awareness! 🙇🏻

Aripander088e2 · 2023-09-22T16:21:57Z

Okay so it is not just me lol

tomfrancis-2211 · 2023-09-22T16:22:36Z

Thank you James, I did a little bit of digging around the GitHub community forums and it seems to be quite a popular issue at the moment

…

On Fri, 22 Sep 2023 at 17:21, James M. Greene ***@***.***> wrote: I'll start investigating. Guessing an upstream change rolled out today. 😓 — Reply to this email directly, view it on GitHub <#225 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEU3IKL5U224WLNR6UPFFILX3W3H7ANCNFSM6AAAAAA5DG57KU> . You are receiving this because you commented.Message ID: ***@***.***>

Aripander088e2 · 2023-09-22T16:23:33Z

Could it be that I was pushing tens of commits out in a short span using the pages

NadyaNayme · 2023-09-22T16:41:14Z

Could it be that I was pushing tens of commits out in a short span using the pages

I started a new repo with a single commit for the purpose of deploying it through Pages and encountered this issue. As others have investigated - it looks like the new request URL broke things.

matthewfeickert · 2023-09-22T16:45:23Z

I think it is safe to say that this is already under investiagation by teams at GitHub (thanks for moving on this fast 🙏), so I think we can all hold tight and wait until things have been resolved.

ChrisHammond · 2023-09-22T16:46:04Z

I think it is safe to say that this is already under investiagation by teams at GitHub (thanks for moving on this fast 🙏), so I think we can all hold tight and wait until things have been resolved.

until I see proof I don't believe! :D

JamesMGreene · 2023-09-22T16:49:01Z

Update: We have identified the issue internally. It is indeed related to an upstream rollout. We'll get the Pages deployment creation endpoint patched ASAP today to handle the new URL patterns. 👍🏻 I'll let you all know when it has shipped but it will probably be a few hours.

ChrisHammond · 2023-09-22T16:50:58Z

Update: We have identified the issue internally. It is indeed related to an upstream rollout. We'll get the Pages deployment creation endpoint patched ASAP today to handle the new URL patterns. 👍🏻 I'll let you all know when it has shipped but it will probably be a few hours.

I believe!

T313C0mun1s7 · 2023-09-22T16:56:05Z

@JamesMGreene It would be a good idea to update the status page. The first troubleshooting step says to check that thing, and to all appearances everything is good. So you have hundreds if not thousands of users assuming this is an issue on their end.

ahsanjb · 2023-09-22T16:56:44Z

:(

v8-j · 2023-09-22T16:59:31Z

@JamesMGreene It would be a good idea to update the status page. The first troubleshooting step says to check that thing, and to all appearances everything is good. So you have hundreds if not thousands of users assuming this is an issue on their end.

My keyboard is banana shaped now

JamesMGreene · 2023-09-22T17:12:53Z

@T313C0mun1s7 Very true. I was trying to establish the actual impact first, which should not be affecting all users as I currently understand it. I've set Pages to status yellow 🟡 now. 👍🏻

jellyfishstar · 2023-09-22T17:21:45Z

I want to cry

T313C0mun1s7 · 2023-09-22T17:29:22Z

@JamesMGreene I literally have a README.md and an extremely simple 10 line index.html, and it is just in the root of my main branch.

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Mastodon Verification for T313C0mun1s7</title>
  </head>
  <body>
    <a rel="me" href="https://fosstodon.org/@T313C0mun1s7">https://fosstodon.org/@T313C0mun1s7</a>
  </body>
</html>

So if it is affecting me, I assumed it affected everyone.

MdNData · 2023-09-22T17:32:22Z

Same issue hopefully the guys are taking care of it! :)

steliancardos · 2023-09-22T17:33:58Z

It-s not working for me either, i only have a index file and it just throws the following errors:
Error: Creating Pages deployment failed
Error: HttpError: Invalid artifact url

T313C0mun1s7 · 2023-09-22T17:41:26Z

Status page just went back to green - It is fixed I presume?

v8-j · 2023-09-22T17:41:33Z

It is fixed :)

T313C0mun1s7 · 2023-09-22T17:43:05Z

Verified, working for me as well.

Ew4n1011 · 2023-09-22T17:51:42Z

Yeah, works for me too.

ericleirosario · 2023-09-22T17:52:18Z

Problema corrigido !

cldwalker · 2023-09-22T17:53:34Z

Works for me too. Thanks @JamesMGreene!

JamesMGreene · 2023-09-22T17:58:29Z

So if it is affecting me, I assumed it affected everyone.

@T313C0mun1s7 Unfortunately, it has nothing to due with a site's complexity, just which artifact servers it ended up using.

Yes, we're back to status green 🟢: https://www.githubstatus.com/incidents/4ypqyv8zbrck

Nearly everyone should be able to successfully create Pages deployments as before, though the last very small slice of users should be fixed in the next hour or so when my internal pull request gets deployed to fully cover the situation.

Thanks to all for your reporting and patience. This one admittedly caught us by surprise, so we'll be sure to improve our monitoring configurations. ❤️

jpzwolak · 2023-09-22T18:47:31Z

works for me now!

matthewfeickert mentioned this issue Sep 22, 2023

minor affil fix matthewfeickert-papers/chep-2023-proceedings-software-citation#3

Closed

JamesMGreene closed this as completed Sep 22, 2023

jcop mentioned this issue Oct 6, 2023

Invalid artifact URL with v1.2.9 #235

Open

JamesMGreene self-assigned this Nov 21, 2023

amblerkr mentioned this issue Dec 18, 2023

Failed to deploy a GitHub action gautamkrishnar/github-pages-gallery#38

Closed

JamesMGreene added the incident Service incident or outage label Dec 27, 2023

ngacho mentioned this issue Oct 9, 2024

actions/deploy-pages v2 failing with HttpError: Invalid artifact url #377

Closed

actions/deploy-pages v2 failing with HttpError: Invalid artifact url #225

actions/deploy-pages v2 failing with HttpError: Invalid artifact url #225

Comments

matthewfeickert commented Sep 22, 2023

jameschensmith commented Sep 22, 2023

GlobalMin commented Sep 22, 2023

Bluefissure commented Sep 22, 2023

viac92 commented Sep 22, 2023

rtvkiz commented Sep 22, 2023 • edited Loading

GlobalMin commented Sep 22, 2023

ghkdqhrbals commented Sep 22, 2023

dgarcu commented Sep 22, 2023

kstiehl commented Sep 22, 2023

v8-j commented Sep 22, 2023

akoroliova commented Sep 22, 2023

jonjoncardoso commented Sep 22, 2023

dahmani-karim commented Sep 22, 2023

ChrisHammond commented Sep 22, 2023

mlettini commented Sep 22, 2023

Ew4n1011 commented Sep 22, 2023

tomfrancis-2211 commented Sep 22, 2023

JamesMGreene commented Sep 22, 2023 • edited Loading

Aripander088e2 commented Sep 22, 2023

tomfrancis-2211 commented Sep 22, 2023 via email

Aripander088e2 commented Sep 22, 2023

NadyaNayme commented Sep 22, 2023

matthewfeickert commented Sep 22, 2023

ChrisHammond commented Sep 22, 2023

JamesMGreene commented Sep 22, 2023

ChrisHammond commented Sep 22, 2023

T313C0mun1s7 commented Sep 22, 2023 • edited Loading

ahsanjb commented Sep 22, 2023

v8-j commented Sep 22, 2023

JamesMGreene commented Sep 22, 2023

jellyfishstar commented Sep 22, 2023

T313C0mun1s7 commented Sep 22, 2023

MdNData commented Sep 22, 2023 • edited Loading

steliancardos commented Sep 22, 2023

T313C0mun1s7 commented Sep 22, 2023

v8-j commented Sep 22, 2023

T313C0mun1s7 commented Sep 22, 2023

Ew4n1011 commented Sep 22, 2023

ericleirosario commented Sep 22, 2023

cldwalker commented Sep 22, 2023

JamesMGreene commented Sep 22, 2023 • edited Loading

jpzwolak commented Sep 22, 2023

rtvkiz commented Sep 22, 2023 •

edited

Loading

JamesMGreene commented Sep 22, 2023 •

edited

Loading

T313C0mun1s7 commented Sep 22, 2023 •

edited

Loading

MdNData commented Sep 22, 2023 •

edited

Loading

JamesMGreene commented Sep 22, 2023 •

edited

Loading