Azure / static-web-apps

Azure Static Web Apps. For bugs and feature requests, please create an issue in this repo. For community discussions, latest updates, kindly refer to the Discussions Tab. To know what's new in Static Web Apps, visit https://aka.ms/swa/ThisMonth
https://aka.ms/swa
MIT License
324 stars 56 forks source link

Upload Timed Out. Unsure if deployment was successful or not. #942

Open ansmah opened 1 year ago

ansmah commented 1 year ago

[error]Error: The process '/usr/bin/bash' failed with exit code 1

When executing from Azure DevOps will get this message sporadically. On subsequent retries we will have some success.

We are using vmImage: ubuntu-latest to execute

mkarmark commented 1 year ago

Can you please provide the app details so we can investigate? If you don't feel comfortable sharing them here, feel free to file a support ticket.

ansmah commented 1 year ago

Can you please provide the app details so we can investigate? If you don't feel comfortable sharing them here, feel free to file a support ticket.

Currently only static content, we have the following files. app.js, config.json, favicon.ico, index.html, readme.md and vancity.css

ssyrell commented 1 year ago

@mkarmark I am also running into this issue. I have an app that is mostly unchanged from the react template. Deploying the app by itself works fine, but as soon as I add an API (I've tried both C# and typescript function apis), I get the timeout issue. It does seem to actually finish deploying, but it takes another 5 or so minutes for the API to show up in the "apis" section of my static web app in the azure portal.

My app can be found here if it helps: https://github.com/ssyrell/purpleair-dashboard

Here is a failed deployment: https://github.com/ssyrell/purpleair-dashboard/actions/runs/3221345766

kaihei777 commented 1 year ago

me too...

MaxWilson commented 1 year ago

Me three. Intermittent timeout failures. Example failure: https://github.com/MaxWilson/POCDungeonDraw/actions/runs/3246742217

Sometimes the live web site gets updated, sometimes it doesn't. I can't detect a pattern except that it several failures in a row are followed by several successes in a row--like it's an environment issue and not an issue linked to my code. Maybe there are certain times of day when load on SWA servers is too heavy?

adam-javelin commented 1 year ago

Having the same issue. Here is my error log: https://pipelines.actions.githubusercontent.com/serviceHosts/583c118f-1d9a-4ddc-862e-67a8e673d75e/_apis/pipelines/1/runs/1258/signedlogcontent/2?urlExpires=2022-10-14T02%3A18%3A10.5877322Z&urlSigningMethod=HMACV1&urlSignature=r038Sm4waknUQMjEtil0wTBx4PKBWIYL0zNCGX16cV4%3D

image

andrewgbell commented 1 year ago

Same issue here as well, details below, but essentially the upload occasionally times out. Once it does, as mentioned in other reports, it will generally fail a few times and then start succeeding a few times. We have less success in the morning (GMT).

DeploymentId: a85c6509-ff2e-4683-81ca-fa3ee09a11e0

App Directory Location: '/build' was found. Looking for event info Skipping step to build /github/workspace/build with Oryx No Api directory specified. Azure Functions will not be created. Either no Api directory was specified, or the specified directory was not found. Azure Functions will not be created. Zipping App Artifacts Done Zipping App Artifacts Uploading build artifacts. Finished Upload. Polling on deployment. Status: InProgress. Time: 2.9537861(s) Status: InProgress. Time: 18.054918(s) Status: InProgress. Time: 33.1716091(s) Status: InProgress. Time: 48.2877535(s) Status: InProgress. Time: 63.4116473(s) Status: InProgress. Time: 78.5275566(s) Status: InProgress. Time: 93.6360356(s) Status: InProgress. Time: 108.7403657(s) Status: InProgress. Time: 123.8702754(s) Status: InProgress. Time: 154.4016648(s) Status: InProgress. Time: 184.6059351(s) Status: InProgress. Time: 199.9511437(s) Upload Timed Out. Unsure if deployment was successful or not.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/ Exiting

HaikoF commented 1 year ago

We have the same problem, using a azure devops pipeline ( task AzureStaticWebApp@0).

dligthart commented 1 year ago

We also have this problem with azure static web app

DavidTheSimon commented 1 year ago

We also have this problem.

FlashITSD commented 1 year ago

Same issue... any workaround?

jmsfilipe commented 1 year ago

Same happening here... Any updates?

mannyyang commented 1 year ago

same issue as well

lohithgn commented 1 year ago

Facing the same issue today ... i created a full stack C# with Blazor & Az Fx all .NET7 ... GH action fails with the error - "Upload timed out. unsure if deoloyment was successful or not" ... and i have a demo in 1 hour time :(

cmclellen commented 1 year ago

Me 4

CalvinQuark commented 1 year ago

I encountered this issue while attempting to follow the Build an Azure Static Web Apps website with Blazor and serverless API tutorial. I tried stepping through this tutorial three times. Each time the Build and Deploy job failed reporting Upload Timed Out. Unsure if deployment was successful or not.

bhavya444 commented 1 year ago

same issue

MaxWilson commented 1 year ago

This issue is back again.

thangcx-3383 commented 1 year ago

same issue

ahkian commented 1 year ago

Same issue for me. `---End of Oryx build logs--- Function Runtime Information. OS: linux, Functions Runtime: ~4, node version: 16 Finished building function app with Oryx Zipping Api Artifacts Done Zipping Api Artifacts Zipping App Artifacts Done Zipping App Artifacts Uploading build artifacts. Finished Upload. Polling on deployment. Status: InProgress. Time: 0.081344(s) Status: InProgress. Time: 15.160747(s) Status: InProgress. Time: 30.2418266(s) Status: InProgress. Time: 45.537767(s) Status: InProgress. Time: 60.7017447(s) Status: InProgress. Time: 75.887511(s) Status: InProgress. Time: 91.1048633(s) Status: InProgress. Time: 106.2816092(s) Status: InProgress. Time: 123.9764901(s) Status: InProgress. Time: 139.1250957(s) Status: InProgress. Time: 154.202578(s) Status: InProgress. Time: 169.2889017(s) Status: InProgress. Time: 185.0700385(s) Status: InProgress. Time: 200.2424887(s) Status: InProgress. Time: 215.3178695(s) Status: InProgress. Time: 230.405882(s) Upload Timed Out. Unsure if deployment was successful or not.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/ Exiting`

abdulpapalek commented 1 year ago

HI is this resolve?, we keep running the same issue for a couple of times now

App Directory Location: 'out' was found. Looking for event info Skipping step to build /working_dir/out with Oryx Using 'staticwebapp.config.json' file for configuration information, 'routes.json' will be ignored. Api Directory Location: 'api' was found. Skipping step to build /working_dir/api with Oryx Function Runtime Information. OS: linux, Functions Runtime: ~4, node version: 16 Zipping Api Artifacts Done Zipping Api Artifacts Zipping App Artifacts Done Zipping App Artifacts Uploading build artifacts. Finished Upload. Polling on deployment. Status: InProgress. Time: 0.263987(s) Status: InProgress. Time: 15.5313462(s) Status: InProgress. Time: 30.8131698(s) Status: InProgress. Time: 46.0440322(s) Status: InProgress. Time: 61.2769718(s) Status: InProgress. Time: 76.4715084(s) Status: InProgress. Time: 91.6647405(s) Status: InProgress. Time: 106.8436189(s) Status: InProgress. Time: 122.1195995(s) Status: InProgress. Time: 137.3141649(s) Status: InProgress. Time: 153.2731447(s) Status: InProgress. Time: 168.4570744(s) Status: InProgress. Time: 183.6682158(s) Status: InProgress. Time: 198.8815765(s) Status: InProgress. Time: 214.1923525(s) Status: InProgress. Time: 229.4028036(s) Upload Timed Out. Unsure if deployment was successful or not.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/ If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/ Exiting

[error]Error: The process '/usr/bin/bash' failed with exit code 1

Finishing: Deploy iot-web-prod

otykier commented 1 year ago

Same issue here. The "Environments" blade in the Azure portal seems to be stuck in the "Uploading" status:

image

eduardotang commented 1 year ago

same issue, and i only find out it did actually deploy successfully when i looked into the "Environments" blade in the portal, the status said "Ready"

cjbadger commented 1 year ago

+1

phranger commented 1 year ago

+1

Just ran through the quick start and how-to guides in the documentation and received this error.

abdulpapalek commented 1 year ago

Got a response from MS from our service request and apparently they found out that the timeout period for the deployment steps is hard coded and if file size is large in combination with some intermittent network issue then you'll encounter this error. The work around that MS suggested to us was either we breakdown our deployments into smaller chunks in the pipeline or deploy in a different time of the day(*When its not very busy which is before lunch time in our timezone) so as a high performing engineer I choose the latter(LOL) .. Its quite annoying cuz this means there is no guarantee that our hotfixes could be deployed in time since there is no guarantee that pipeline wont fail especially in the afternoon

zjhch123 commented 1 year ago

@abdulpapalek do they offer any ETA for the fixing? I can't imagine they hard-code such a critical variable... 🤬

abdulpapalek commented 1 year ago

@zjhch123 not really, i dont think they are fixing it anytime soon which is a bummer because we'll be adding 2 new big packages

AntoineSmet commented 1 year ago

Ok I find a solution just add

- app_build_timeout_seconds: 1800

on your file yml

abdulpapalek commented 1 year ago

@AntoineSmet that is only for the build. Unfortunately there is no easy way around the deployment polling timeout. This is the sample code that MS sent us

Screen Shot 2023-05-24 at 11 17 20 AM

kianryan commented 1 year ago

We've just had the same problem on a critical site. Deployment before 0900 before business hours, showing as "Uploading", but never resolving. Multiple deployments not resolving. This is /not/ a large deployment, but "wait until quiet" is not an acceptable solution.

DavidVollmers commented 1 year ago

Same issue for me since yesterday...

roldengarm commented 12 months ago

Yes, I also have the same issue, very frustrating. It was working fine when set up initially in March, but recently have seen this error occur randomly.

Is there any workaround or solution?

Perhaps a solution/hack is to implement a retry with e.g. https://github.com/Wandalen/wretry.action

DavidVollmers commented 12 months ago

@roldengarm So for me at least it is working again. It seems to be a temporary, yet reoccuring problem...

celsocoutinho-tangany commented 12 months ago

I also had this issue a few days back for the first time, during my holidays, and redeploying now worked! A bit frustrating, especially considering the workaround given by MS

roldengarm commented 12 months ago

@roldengarm So for me at least it is working again. It seems to be a temporary, yet reoccuring problem...

Yes, it is always working the second time, but it is very annoying as I have to re-run our pipeline manually.

rosemcc commented 9 months ago

Same issue here. Is there any update on this?

hgbao commented 9 months ago

Having the same issue here. And the environment has been stuck at Updating for days now. But the new code has already been uploaded successfully image

GiladGershon commented 7 months ago

same issue

tejaswankalluri commented 7 months ago

Same issue image

bluewilliams commented 7 months ago

Same issue here. Start time of the event appears to be timed with a significant outage of the GitHub Actions/Runner workload which has subsequently been resolved a couple hours back.

cite: https://www.githubstatus.com/history

58836980 commented 7 months ago

Same issue from today, it happens only in Production. Staging deployments are OK.

tejaswankalluri commented 7 months ago

Same issue here. Start time of the event appears to be timed with a significant outage of the GitHub Actions/Runner workload which has subsequently been resolved a couple hours back.

cite: https://www.githubstatus.com/history

Yes but runners are working fine now. but still showing the same error

tejaswankalluri commented 7 months ago

created a new issue #1396

javiercoh commented 7 months ago

same here

rezwanul-islam commented 7 months ago

Re-run the same job in a different time. It might help.

elad320011 commented 6 months ago

I get this error in Azure Devops after 600 seconds. Is there a resolution already?

Cypher1 commented 6 months ago

I'm seeing this with the Github Actions Deploy in a staging build for a PR.

thomasgauvin commented 6 months ago

@elad320011 @Cypher1 are you deploying Next.js workloads? If so, can you share the region of your static web apps and its default hostname/url in the thread https://github.com/Azure/static-web-apps/issues/1427?