You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
A clear and concise description of what you expected to happen.
Environment
Information on your environment:
* Language name and version: c#, sdk 9.0.200, OS Ubuntu 22.04
* IDE and version : No IDE, using CLI via Azure Devops Pipelines
Additional context
Add any other context about the problem here.
OwenCross289
changed the title
AZD deploy getting stuck on (Uploading deployment package) as of yesterday
AZD deploy getting stuck on (Uploading deployment package) as of 2024/02/24
Feb 25, 2025
I am running into a similar issue when deploying a streamlit application to Azure App Service.
After a while, the responses are status code 500 (instead of 202), BUT this seems to only affect the streamlit deployment (and not other Apps hosted on Azure App Service) for now.
Your observations does seem to be conclusive here, App Service isn't behaving the way we'd expect it to. The general troubleshooting strategy I'd recommend is to open up the App Service resource in Azure and navigate to deployment logs. There may be more detailed logs there.
If more help is needed at any point, an Azure support request may also be useful avenue.
Output from
azd version
Run
azd version
and copy and paste the output here:azd version 1.12.0 (commit dc37b93)
Describe the bug
Deploying multiple services with AZD up to azure appservice the second service (add likely 3rd) gets stuck on
To Reproduce
use an azure.yaml like this
Expected behavior
A clear and concise description of what you expected to happen.
Environment
Information on your environment:
* Language name and version: c#, sdk 9.0.200, OS Ubuntu 22.04
* IDE and version : No IDE, using CLI via Azure Devops Pipelines
Additional context
Add any other context about the problem here.
When splitting out the deployment from
azd up
todeployment succeeds.
Secondly this appears to be an azure api issue? as when I apply --debug the second service gets stuck in this loop
The text was updated successfully, but these errors were encountered: