Deployment Failed on Azure Web App (Python Flask App)

Question

I had a python flask app deployed successfully on web app. However, recently when I tried to redeploy the app, the deployment failed with a status 3 and no status text. I didn't make any changes to the web app setting.

The only difference I found between my succeed deployment logs and current failed deployment logs is below: (part of the "Running oryx build...”)

• Succeed:

Copying files to destination directory '/tmp/_preCompressedDestinationDir'...
Done in 174 sec(s).
Compressing content of directory '/tmp/_preCompressedDestinationDir'...
Copied the compressed output to '/home/site/wwwroot'
 
Removing existing manifest file
Creating a manifest file...
Manifest file created.
Copying .ostype to manifest output directory.
 
Done in 2111 sec(s).

• Failed:

copying files to destination directory '/tmp/_preCompressedDestinationDir'...
Done in 164 sec(s).
Compressing content of directory '/tmp/_preCompressedDestinationDir'...
\n/bin/bash -c "oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.8 -p virtualenv_name=antenv --log-file /tmp/build-debug.log  -i /tmp/8dba9123337e81c --compress-destination-dir | tee /tmp/oryx-build.log ; exit $PIPESTATUS "

Could it be caused by github? My app requires a large storage in github, so my github account's Storage for Actions and Packages is used up, but it also says "Actions should still work correctly at this time.".

Answer 1

@Violet Zeng It seems that the deployment of your Python Flask app on Azure Web App has failed with a status 3 and no status text. The difference between the successful and failed deployment logs is that the failed deployment log has an additional line of code that specifies the platform version of Python.

Regarding your question about whether the issue could be caused by GitHub, it is unlikely that the storage limit of your GitHub account is causing the deployment failure. However, it is always a good idea to check if there are any issues with your GitHub repository.

To troubleshoot the issue, you can try the following steps:

Check the deployment logs:

• Go to the Azure portal and navigate to your Web App.
• Click on "Deployment Center" in the left-hand menu.
• Click on "Logs" to view the deployment logs.
• Look for any error messages or warnings that might indicate the cause of the failure. Common issues include missing dependencies, syntax errors, or permission issues.

Check your GitHub repository:

• Make sure that you have the correct authentication credentials set up for your GitHub repository.
• Check if there are any issues with your repository, such as insufficient permissions or storage limits.
• Make sure that your code is up-to-date and there are no syntax errors.

1. Redeploy your app:

• Make sure that your code is up-to-date and there are no syntax errors.
• Try deploying your app again using the same deployment method that you used before.
• If the deployment still fails, try using a different deployment method, such as FTP or Git.