Linux Web App Zip Deploy stuck on polling Kudu #16936
Comments
github-actions
bot
added
Area: Release
bug
environment:need-to-triage
|
We've also observed this behavior on several of our runs. @nadesu any update on this? |
|
This issue has also occurred for me various times in the past and currently today when I am doing a deployment. Previously occasionally disconnecting in deployment center for the slot would resolve the issue. Today, that is not the case. I have seen others say that deleting the slot and recreating will resolve it. This is not a great answer. I suspect that this is an issue with zip deploy and/or linux app services, as I have never encountered this using web deploy with windows app services. Zip Deploy appears to be the only option for linux app services, so there don't appear to be many options here. Edit: I was able to get this working again by deleting the locks and deployment directories via ssh. I would have also disconnected in deployment center if that was an option, but it was not this time. Subsequent deployment did not run into an issue being stuck in polling. |
|
We've also observed this behavior on several of our runs. @nadesu any update on this? We are using "Web App on Windows" as App Service name. |
|
We are having exactly the same issue. 2023-05-24T10:18:21.0051539Z ##[debug]Deployment status: 0 'Receiving changes.'. retry after 5 seconds keeps going on an azure function app hosted on linux 57 minutes now on the deploy task and counting |
|
Could we get an update on this issue or a workaround or something? This seems to happen fairly often with our linux based function apps. |
|
Same issue here, do we have any updates? |
|
Any updates on this? running through the same issue |
|
Observing the same behaviour regularly, any news or reasons for it? |
|
Observing the same behavior, across several of our applications. We have reported this directly to our Microsoft partners and the only feedback they give is to change the timeout value of the process (which obviously doesn't solve the problem, just reduces its impact). Can we get somebody, anybody, at MS to take this seriously?! |
|
We had to resort deleting the staging slots then letting them be recreated with our ARM task first, when we deploy into them to try to workaround this issue which seemed to improve the situation a bit. We think this might have something to do with previous deployment packages somehow getting stuck in the slot we are deploying to. |
|
Had a function on consumption plan and then moved it to a dedicated app service and now i cant deploy any longer. if i retry enough times it seems to go through anyway. often the pipeline says deployment failed, but it did succeed. seeing the same retry error also if it doesnt fail. other times the logs just say "Package deployment using ZIP Deploy failed. Refer logs for more details." |
|
We regularly run into this with all of our function apps that are on a dedicated app service plan. Happens with both AzureFunctionApp@2 and AzureFunctionApp@1 tasks. |
|
I'm still experiencing this issue |
|
same issue here: |
|
I have the same error :( |
|
Same issue here. |
|
Any news on this ? we are having this issue too, so many pipelines get stuck randomly because of this |
|
Same issue here. Any good workarounds? |
|
Use website run from package option
Regards,
Sergey
…On Mon, 12 Feb 2024 at 17:01, Lassi Mustonen ***@***.***> wrote:
Same issue here. Any good workarounds?
—
Reply to this email directly, view it on GitHub
<#16936 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACTU2WZC6AJGFA7AAYCX4ODYTI4G3AVCNFSM6AAAAAAQR6JX46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYHE4DQMRXGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I managed to run the pipeline successfully. Added |
|
Same issue started last Friday July 19. Tried recreating the app, recreating the pipeline, stopping the service, restarting the service and nothing worked. The only workaround that worked was to change the deployment method to |
|
Fwiw @rob90404 and others - I'd faced several issues including this one with no resolution. Or worse, it was resolved but I had no idea how it was resolved. We moved to App Service with container deployment instead of file deployment and have been able to sleep peacefully ever since :) Zip deployment:
Container deployment:
No issues so far with Container deployment. Here's my Github Action in case it helps. It's pretty simple (this is generally auto-created when you add inputs in the Azure portal for App Service Container Deployment) # Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
# More GitHub Actions for Azure: https://github.com/Azure/actions
name: Build and deploy container app to Azure Web App
on:
push:
branches:
- master
workflow_dispatch:
jobs:
build:
# Let Github Actions build the container for you
runs-on: 'ubuntu-latest'
steps:
- uses: actions/checkout@v2
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
- name: Log in to registry
uses: docker/login-action@v2
with:
registry: https://ghcr.io/ # In case you want to use Github to store the containers you build
username: ${{ secrets.your-secret-here }}
password: ${{ secrets.your-secret-here }}
- name: Build and push container image to registry
uses: docker/build-push-action@v3
with:
push: true
tags: ghcr.io/${{ secrets.your-secret-here/company/repo-name/prod:${{ github.sha }}
file: ./Dockerfile
deploy:
# Azure's turn now - just deploys it
runs-on: ubuntu-latest
needs: build
environment:
name: 'production'
url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}
steps:
- name: Deploy to Azure Web App
id: deploy-to-webapp
uses: azure/webapps-deploy@v2
with:
app-name: 'alloan-v2-prod-app'
slot-name: 'production'
publish-profile: ${{ secrets.your-secret-here }}
images: 'ghcr.io/${{ secrets.your-secret-here/company/repo-name/prod:${{ github.sha }}'
Here's a Dockerfile sample for you to start with: # syntax=docker/dockerfile:1
# Depending on if you use python/node etc
FROM python:3.11
RUN apt-get update && apt-get install -y curl && \
curl -sL https://deb.nodesource.com/setup_21.x | bash - && \
apt-get install -y nodejs
# Set initial directory
WORKDIR /code
COPY . .
# Python setup sample
RUN pip3 install -r requirements.txt
# Run tests if you want
RUN python3 -m pytest path/to/your/test/* -v
# Node setup sample
WORKDIR /code/your-frontend
RUN npm install -g yarn
RUN yarn install
RUN ls
RUN yarn run build
WORKDIR /code
# Once you build frontend, raw files aren't needed anymore
RUN rm -rf /code/your-frontend
# The equivalent of console.log() if you want to debug
RUN ls
RUN cd frontend-dist && ls
EXPOSE 50505
ENTRYPOINT ["gunicorn", "app:app"] |
|
I faced the same issue, deployment to window OS is fine (20s), but to linux stuck up to more than 10 minutes. Workfaround for me: disable System.Debug from Variables, it speed up to only 40s. |
Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureWebApp@1
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment
Server - Azure Pipelines or TFS on-premises?
Azure Pipelines
Agent - Hosted or Private:
If using Hosted agent, provide agent queue name:
Agent name: 'Azure Pipelines 4'
Agent machine name: 'fv-az234-54'
Current agent version: '2.210.1'
Operating System
Ubuntu
20.04.5
LTS
Issue Description
Deployment of a Linux Web App inconsistenly hangs on REST operations towards KUDU. With enough re-deploys it will after a while work. In the deployments where it hangs it will fail at around 25 minutes with an unknown error.
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
The text was updated successfully, but these errors were encountered: