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

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?

About this issue

  • Original URL
  • State: closed
  • Created 9 months ago
  • Reactions: 9
  • Comments: 42 (4 by maintainers)

Most upvoted comments

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’ll start investigating. Guessing an upstream change rolled out today. 😓 Thanks for raising our awareness! 🙇🏻

@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.

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. ❤️

@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. 👍🏻

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

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

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.

@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

I want to cry

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.

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.

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