deploy-pages: Getting `deployment_perms_error` when trying to run this action since June 16
Two days ago (June 16) this action stopped working. This is the first run where I’ve seen it fail - https://github.com/idanarye/bevy-yoleck/actions/runs/5293695779/jobs/9592352399.
When I look at the logs, I see these lines repeating 5 times after the Created deployment for <...>, ID: <...> log:
Getting Pages deployment status...
Current status: deployment_in_progress
And then these lines repeating over a hundred times:
Getting Pages deployment status...
Current status: deployment_perms_error
Followed by:
Error: Timeout reached, aborting!
Error: Timeout reached, aborting!
Canceling Pages deployment...
Canceled deployment with ID <...>
Note that:
- I’ve upgraded from v1 to
actions/deploy-pages@v2, but the problem still repeats. - When I tried to rerun older runs that did pass, this action failed.
So I think maybe something was changed in GitHub that either broke this action or caused it to require some additional configuration/permissions.
Note that six hours before that first failed run linked above I had a run that managed to pass and deploy the pages: https://github.com/idanarye/bevy-yoleck/actions/runs/5285227962/jobs/9563650017. So whatever changed probably happened during these six hours.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 5
- Comments: 17 (4 by maintainers)
Commits related to this issue
- Fix invalid permissions The website deployment action has been failing lately. Looking at the issue, it seems to be related to https://github.com/actions/deploy-pages/issues/188 that is due to https:... — committed to ServiceWeaver/weaver by rgrandl a year ago
- Fix gh pages permissions, as instructed in actions/deploy-pages#188 — committed to DCNick3/shin by DCNick3 a year ago
- Fix invalid permissions (#410) The website deployment action has been failing lately. Looking at the issue, it seems to be related to https://github.com/actions/deploy-pages/issues/188 that is due to... — committed to ServiceWeaver/weaver by rgrandl a year ago
- Fix documentation publishing (#531) Fixes #517. Relates to https://github.com/actions/deploy-pages/issues/188 — committed to DigitalExtinction/Game by Indy2222 a year ago
- Try fix file premissions ref: https://github.com/actions/deploy-pages/issues/188 — committed to sphinx-notes/pages by SilverRainZ a year ago
- Fix file permissions before deployment to GitHub Pages See https://github.com/actions/deploy-pages/issues/188#issuecomment-1597613954 for more details. This will avoid timeouts like this: Getti... — committed to noritada/rrr-rs by noritada a year ago
- Fix file permissions before deployment to GitHub Pages See https://github.com/actions/deploy-pages/issues/188#issuecomment-1597613954 for more details. This will avoid timeouts like this: Getti... — committed to noritada/rrr-rs by noritada a year ago
- Fix docs deploy file perms https://github.com/actions/deploy-pages/issues/188 — committed to unsplash/mercury by samhh a year ago
- Fix docs deployment (file permissions) See: https://github.com/actions/deploy-pages/issues/188 — committed to neuppl/rsdd by mattxwang a year ago
- Fix docs deployment (file permissions) (#112) See: https://github.com/actions/deploy-pages/issues/188 — committed to neuppl/rsdd by mattxwang a year ago
- Update build artifact permissions I found other users reporting a similar issue: https://github.com/actions/deploy-pages/issues/188 The root cause seems to be that the deploy-pages action changed t... — committed to llvm-beanz/DirectXShaderCompiler by llvm-beanz a year ago
- Update build artifact permissions (#5387) I found other users reporting a similar issue: https://github.com/actions/deploy-pages/issues/188 The root cause seems to be that the deploy-pages acti... — committed to microsoft/DirectXShaderCompiler by llvm-beanz a year ago
- No longer need to fix file permissions As https://github.com/actions/deploy-pages/issues/188 got fixed. — committed to sphinx-notes/pages by SilverRainZ 5 months ago
Hopefully that was just it, although I feel like this should have been a breaking version bump on
@actions/upload-pages-artifact? 😄Apologies for not getting the documentation published on time.
If you get a permissions issue, that means your artifacts are not in the form we expect. You can fix that with an extra step, see https://github.com/actions/upload-pages-artifact#file-permissions (as per @YiMysty above 🙇).
We used to proactively fix permissions on your behalf but for many sites (with lots of files), that would delay Pages deployments by a lot and not be needed. We decided to just surface the error slightly better and document a mitigation step. Also note that this typically only happens if you have a custom workflow (dockers builds can be impacted).
It worked!
Just a note here from me, turns out that the only file with incorrect permissions for my Rust based project was the
.lockfile that Cargo had snuck in to my rustdoc build 😄@onbjerg
I agree. I’m going to revert that change in the
v1line forupload-pages-artifactand cut a newv2.0.0/v2release for thechmodremoval. Sorry about that! 😅I’ll drop an update here once that’s cleaned up.
@onbjerg Updates on
actions/upload-pages-artifact: 🚀chmodcommands have been added back inv1.0.10and the latestv1major tagchmodcommands have been removed (again) inv2.0.0and the newv2major tagThanks again for the constructive feedback! 🙇🏻
I’ve just checked in my repo, and the deployment does not update - I’m still getting the ones from the last successful deploy from before June 16. But the “Last deployed” in the “GitHub Pages” setting does update.
@onbjerg I could not. The error is about permissions, so I tried adding more permissions that maybe could have been related (specifically I tried
deployments: writeandactions: write. They probably don’t matter, but I was just trying things out) but it didn’t work.