Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The new feature "Show status during deployment for linux apps" gets stuck waiting

See original GitHub issue

Describe the bug

Command Name az webapp deployment source config-zip

The command gets stuck waiting seemingly forever for some build to finish even though the zip already deployed just fine.

WARNING: Getting scm site credentials for zip deployment
WARNING: Starting zip deployment. This operation can take a while to complete ...
WARNING: Deployment endpoint responded with status code 202
/ Running...

| Running...

\ Running...
BuildRequestReceived...          
BuildRequestReceived...          -
BuildRequestReceived...          Success! 
BuildPending...                  

BuildPending...                  /
BuildPending...                  Success! 
BuildInProgress...               

BuildInProgress...               |

BuildInProgress...               \

BuildInProgress...               -

BuildInProgress...               /

“BuildInProgress…” then just repeated for more than 5 minutes before I aborted, normally I can deploy in 15-30 seconds.

To Reproduce

I deployed to a stopped slot which my scripts starts up after the deploy is completed, I’m not sure if that is the cause. I did start the slot manually after a couple of minutes and verified that the deployment was indeed working but Azure CLI just kept on printing “BuildInProgress…”

The reason I deploy to a stopped slot is so I don’t start an old version of the site since it’s just going to be replaced with a new version anyway.

Expected Behavior

Deployment should not get stuck waiting for something that is already completed.

Environment Summary

Linux-5.10.0-16-amd64-x86_64-with-glibc2.31, Debian GNU/Linux 11 (bullseye)
Python 3.10.5
Installer: DEB

azure-cli 2.40.0

Additional Context

It’s a zip deploy, there shouldn’t be a build step. The Kudu deployment API lists the following times:

"received_time" : "2022-09-17T19:46:01.6550694Z",
"start_time" : "2022-09-17T19:46:02.945671Z",
"end_time" : "2022-09-17T19:46:03.9086207Z",
"last_success_end_time" : "2022-09-17T19:46:03.9086207Z",

It seems to me the deployment completed in just over 2 seconds so Azure CLI has no reason waiting for over 5 minutes.

I believe it was #23464 that introduced this unwanted behavior.