-
Notifications
You must be signed in to change notification settings - Fork 75
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 404: When request Azure resource at PublishContent, zipDeploy : Failed to use /home/runner/work/_temp/temp_web_package_...zip as ZipDeploy content #216
Comments
This issue keeps occurring randomly for our deployments. :( |
same here too. Microsoft fix this please! |
@patelchandni @Hazhzeng any ideas how to solve this problem? |
Same here |
Same here, I have error but it's deploy |
Any solutions inbound? Having the same issue with v1.5.0 and 1.5.1 |
Same thing here - the builds suddenly started failing after 2 years. My workaround for now is to use https://github.com/Azure/webapps-deploy instead. Found the workaround in another related issue: #213.
|
Same issue here as well... |
same issue here |
same issue here! |
Same issue here! |
Any alternative solutions to propose ? |
+1 |
Hello Allo,
Hope this can help you ! |
+1 |
1 similar comment
+1 |
Same issue here. |
Hey this issue is still existing for me. The re-deploy mentioned previously is not working, is there any attention on this? |
I got a similar error message in my workflow and have been trying to solve it for several days. I'm using RBAC instead of publish-profile, but maybe this still applies and helps someone: I disconnected the leftover configuration in the functions Deployment center (menu in Azure portal), even though I was NOT deploying through it, but through GitHub runner with RBAC credentials. No actual changes to the workflow itself or environment variables (I do have the |
These github workflows have worked 2 years for us to deploy various python functions hundreds of times to azure and now are suddenly no longer reliable:
While debugging now we also tried v1.5.1, but no success with it either. Some more or less random restart/delete/disable may or may not help to resolve it (as described here microsoft/azure-pipelines-tasks#18739 (comment)) but the issue comes back and then one can start the deployment over and over again and see the same error.
Here is how the github job log starts with debug logging:
And this is how it fails:
It does seem to finish the publishing though (as our version tag shows the new version) but it does not start the remaining steps of the deployment as it considers this step as failed.
The text was updated successfully, but these errors were encountered: