Deployment Fails with Timeout of App Setting Update on SCM

[khkh-ms]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az functionapp deployment source config-zip

Describe the bug
Setting app settings on scm site (instead of actual zip deployment) fails. App Setting update on SCM site happens before the actual deployment. When trying to fetch the current settings from SCM site, it fails with timeout because the GET request has 3 seconds timeout. SCM normally takes more than 3 seconds to wake up.

To Reproduce
The issue happens randomly therefore it is not easy to reproduce.

Expected behavior
Get Setting should not timeout in 3 secs.

Environment summary

Additional context

[kamperiadis]

It looks like this is a duplicate of this issue There is a timeout option for the az functionapp deployment source config-zip command that might help.

[yonzhan]

route to CXP team

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Stefanus Hinardi, @Francisco-Gamino.

Issue Details

---

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

az functionapp deployment source config-zip

Describe the bug
We don't have reasonably long timeout/retry with zip deployment. Sometimes SCM sites takes long time to start. In that situation, the deployment fails with the timeout.

To Reproduce
The issue happens randomly therefore it is not easy to reproduce. It might happen more often on when you deploy reasonably large app on a small SKU though (The issue is not limited to small SKUs).

Expected behavior
Deployments normally take long time. We should have longer timeout.

Environment summary

Additional context

Author:	khkh-ms
Assignees:	-
Labels:	Service Attention, Functions, Auto-Assign
Milestone:	Backlog

[navba-MSFT]

Adding Service teams to look into this.

@Stefanus Hinardi, @Francisco-Gamino. Could you please look into this ?

@khkh-ms Since you are internal to Microsoft, I will loop you with the Product Group team who were assisting on this issue: #24644 You can take this discussion forward.