Azure Release pipeline failing to deploy Flask Python Web APP

Question

Azure Release pipeline failing to deploy Flask Python Web APP with below error. Manual deployment is working fine.

2024-04-17T04:55:44.5177716Z Fetching changes.
2024-04-17T04:55:45.1608614Z Cleaning up temp folders from previous zip deployments and extracting pushed zip file /tmp/zipdeploy/29d8ab60-51cc-4fc0-a802-65c616f63ece.zip (93.15 MB) to /tmp/zipdeploy/extracted
2024-04-17T04:55:45.1652212Z ##[error]Failed to deploy web package to App Service.
2024-04-17T04:55:45.1667263Z ##[warning]Can't find loc string for key: KuduStackTraceURL
2024-04-17T04:55:45.1669167Z ##[error]KuduStackTraceURL https://$GhostX-WebAPI-Dev:***@ghostx-webapi-dev.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace
2024-04-17T04:55:45.1670770Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.

Answer 1

@Priyanka Hurakadli It seems like there is an issue with the deployment of your Flask Python Web App using Azure Release pipeline. The error message suggests that the package deployment using ZIP Deploy has failed.

To troubleshoot this issue, you can check the logs for more details. The KuduStackTraceURL provided in the error message can be used to access the logs. You can try to access the URL and see if it provides any additional information about the error.

In addition, you can also try the following steps to resolve the issue:

1. Check if the required dependencies are installed on the Azure App Service. You can check this by navigating to the "Configuration" tab of your App Service and checking the "Python version" and "Virtual environment" settings.
2. See if the deployment package is correctly configured. Make sure that the package contains all the required files and dependencies.
3. Try deploying the web app manually to see if it works. If it works, then there might be an issue with the Azure Release pipeline configuration.
4. Ensure the Azure Release pipeline is configured correctly. Make sure that the pipeline is configured to deploy the correct package and to the correct App Service.

Let us know the outcome by replying here.