azure-cli: az functionapp deployment source config-zip keeps retrying even though deployment failed with 503 Service Unavailable

On azure-cli 2.0.80 (did not try other versions), publishing code to a Linux Function App will cause the command to keep retrying even though publishing the code failed with 503 Service Unavailable:

$ az functionapp deployment source config-zip --resource-group example-61-linux --name functionappasdwq61 --timeout 180 --src function.zip
Setting ENABLE_ORYX_BUILD to false
Setting SCM_DO_BUILD_DURING_DEPLOYMENT to false
Getting scm site credentials for zip deployment
Starting zip deployment. This operation can take a while to complete ...
Deployment endpoint responded with status code 503
Deployment status endpoint https://functionappasdwq61.scm.azurewebsites.net/api/deployments/latest returns malformed data. Retrying...
Deployment status endpoint https://functionappasdwq61.scm.azurewebsites.net/api/deployments/latest returns malformed data. Retrying...
  [...]

My expectation was that the command would fail as soon as it notices that the deployment endpoint responds with status code 503, as there’s no sense in retrying at that point.

(To be clear, this issue is not about the deployment failing with 503 Service Unavailable; it is about how Azure CLI handles the 503.)

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 3
Comments: 20 (1 by maintainers)

Most upvoted comments

Just experienced this issue with az webapp up - fixed it by increasing the tier of the App Service Plan from F1 to B1

Might help in case anyone else experiences this issue in the future. YMMV

nagyben on Nov 17, 2021

I can also confirm that this seems to be a resource issue. Upgrading my service plan fixed it.

Particularly it seems to be an issue with maxed out CPU

you can see above where I upgraded (drop in CPU). The second spike is my performing a release. So releasing seems to be quite CPPU intensive and if you don’t have enough CPU it hangs. Could really do with better messaging around this TBH

sonic1981 on Sep 29, 2020

The same problem. When I create a new empty function app using any method (tried just portal web UI) on ASE and try to navigate to its scm endpoint it returns 503. It can take about 10 minutes before this endpoint is available. ASE runs on test environment with Isolated pricing tier:

I1
210 total ACU
3.5 GB memory
Dv2-Series compute equivalent

But this issue never happened before.

UPDATE: It turned out to be a performance issue - App Service Plan had almost 100% CPU and Memory usage.

ivan-sam on Sep 2, 2020

Facing the same problem, sometimes it works, other times it doesn’t.

kbooth-insight on Jun 25, 2020