.NET Core 3.0 Availability on App Service

[fabiocav]

Discussion for .NET Core 3.0 Availability on App Service.

[lanehoy]

Sound good. And what about App Service Linux ?

[fabiocav]

App Service Linux is also coming very soon. We'll post an update there with details once that information is available.

[sjkp]

What else is included in this update? My Lets Encrypt site extension, that host a few webpages on the are starting to get 502 gateway errors. The errors starting being reported by users in US regions about a week ago, but now all regions seems to be affected, West Europe being hit today. Given that the errors have slowly spread I think it is on the infrastructure level, so I have no chance to debug this.
People are reporting it here: sjkp/letsencrypt-siteextension#331

[sjkp]

People are reporting similar issues for the standard kudu portal: Azure/azure-webjobs-sdk#2343
I also get the 502 gateway error on POST request, all my get requests work fine.

[fabiocav]

@sjkp do you have more details on the exception/error seen? Would you be able to share a site name for investigation?

[tmenier]

@fabiocav I can provide some details on what I'm seeing:

• Continuous WebJobs
• .NET Framework
• WebJobs SDK
• [NoAutomaticTrigger] (or any trigger attribute that makes them show up in Kudu)

Repro: Click "Run" button on any function in Kudu. Spins for 2 minutes and returns this:

So far Azure support is stumped and so am I. But the timing seems to line up perfectly with this release. Note that we're seeing it with multiple completely isolated production WebJobs that haven't had code changes in a while, as well as totally trivial test WebJobs deployed solely to troubleshoot this issue. All suddenly started experiencing this last Friday (10/4) morning.

[sjkp]

@fabiocav you can browse my test site here (with a dummy extension that does a simple post request which fails)
https://webappcfmv5fy7lcq7o.scm.azurewebsites.net/dummyapp/

I just deployed an empty MVC app with no functionality other than a controller that accepts a POST request and it fails too. So it has nothing to do with my extension.

My sample site extension that shows the problem is uploaded here
https://github.com/sjkp/azure-site-extension-502

It is also available as a site-extension here https://www.nuget.org/packages/dummyapp/

Here is a failed request log https://github.com/sjkp/azure-site-extension-502/blob/master/https____1webAppcfmv5fy7lcq7o_80_dummyapp_%2C%20STATUS_CODE%20500%2C%20124750%20ms%2C%20POST.xml

There is a 2 minute gap between the different modules, I have no clue how to debug that futher.

[fabiocav]

@sjkp thank you for all the details. We're taking a look at the issue and will provide updates here.

[fabiocav]

@sjkp was this test site extension deployed onto an existing resource group/app? do you see the same issue if you deploy to a different app/resource group/plan?

[mathewc]

@sjkp I'm able to browse the https://webappcfmv5fy7lcq7o.scm.azurewebsites.net/dummyapp/ site without error - the ASP.NET page loads for me. Similarly for https://webappcfmv5fy7lcq7o.scm.azurewebsites.net/letsencrypt

[sjkp]

@mathewc @fabriocav get requests are working fine, so you can browse the two extension, but when you try a POST request they both fail. You can click the "next" button to initiate a POST request.

[tuin007]

Got any fix forecasts? I can no longer add to new domains.
I have this same problem here Southern Brazil

[mathewc]

@tuin007 what are your repro steps? Trying to determine if this is occurs only in site extensions.

[tuin007]

Playback: Click the "Run" button in any Kudu function. Turns for 2 minutes and returns: Server Error 502

Next:

Return error:

[mathewc]

@sjkp The POST requests via the "Next" buttons in your webappcfmv5fy7lcq7o app all succeed for me when trying:

[tmenier]

@mathewc I don't know if my issue is related or not, but this is the call that is failing for us, invoked by simply clicking the "Run" button on any WebJob function in Kudu:

POST https://myappservice.scm.azurewebsites.net/azurejobs/function/Run?functionId=xxxx

Can you confirm with any trivial WebJobs function using the SDK that clicking "Run" in Kudu works? I initially reported this here and have since gotten a couple other reports of the same behavior. If this is in fact a different issue than the one being discussed here, would you mind replying to that issue as well? Thanks!

[fabiocav]

Just as an update; the issue above is not related to the .NET Core 3.0 deployment. The deployment is moving forward while we continue to investigate the problem.

[sjkp]

@mathewc that is very strange. Because it doesn't work for me whatsoever.

[mathewc]

We are able to repro with the repro project you posted above however, and we’re investigating. Repros on a machine without .NET Core 3.

[sjkp]

Okay - it just started around the rollout of .net core 3. But it can ofc, be something else like a windows update.

[shibayan]

It seems that .NET Core 3.0 Runtime is available in some regions 👍 , but will the .NET Core 3.0 SDK not be updated at the same time?

[CarljohanDanling]

It seems that .NET Core 3.0 Runtime is available in some regions 👍 , but will the .NET Core 3.0 SDK not be updated at the same time?

Where can you find/see this information?

[pseabury]

@CarljohanDanling https://aspnetcoreon.azurewebsites.net/

[pseabury]

Also - Is the Runtime selection box for App Services tied to the SDK, or the installed runtimes? It appears that for all the US regions that have the Core 3 runtime installed, you can still only choose 2.2 runtime.

[Kormyr]

Thanks, we have our first Asp.net Core 3 application running on a West EU App Service 👍

[justdmitry]

@Kormyr build locally and published via VS, or auto-build in AppService after push into git ?

[Kormyr]

@justdmitry Auto-built on ADO and auto-deployed in App Service after push into Git

[Link-69]

The deployment is said as complete but I still can't find 3.0 when creating a new web app on Azure?

[vinay-chaudhari]

@timheuer, .NET Core 3.0 runtime is available from SSH. Checking applications logs - I can see two issues; one is from kestrel "Unable to bind to http://localhost:5000 on the IPv6 loopback interface: 'Cannot assign requested address'". Another is about Container didn't start in expected time limit - I guess it must be the side effect of first one. Any idea how to go about debugging this one?

[vinay-chaudhari]

@timheuer, tried deployment of same project on windows and it works. On Linux app service, its failing to start with container didn't start in expected time limit. I have migrated this project from 2.2 to 3.0. Any ideas about how to troubleshoot this issue...

[timheuer]

@vinay-chaudhari That's an error message I've not come in to myself. I saw some references to this and Kestrel here aspnet/IISIntegration#239 but maybe @bradygaster can shed some light on this?

[bradygaster]

@vinay-chaudhari did you try removing the 5000 port to see if it will spin up onto the default port 80? Also - do you have UseHttpRedirection uncommented? Curious if you're trying to hit your site via HTTP or HTTPS.

[vinay-chaudhari]

@bradygaster how do I remove 5000 port? I know for dev environment, its in launchsettings.json but not sure where do you set for production. As far as your queries foes, I have UseHttpsRedirection and I am hitting the site via https only.

[ctolkien]

Any update now re: 3.1 timelines ?

[fabiocav]

3.1 runtime deployment will begin soon (by end-of-week) and we'll have a new announcement once happens.

[marchy]

@fabiocav @timheuer what's the update on being able to deploy .NET Core 3.0 on Azure from Deployment Center? It's been 2+ months now and we still can't deploy anything beyond .NET Core 2.2 – nor have you set up any tracking to communicate what issues are outstanding/blocking it.

[fabiocav]

@marchy SDK deployments will start shortly after the runtime release. This will actually have 3.0 and 3.1 SDKs.

We'll follow up here (and in the 3.1 announcement) once that starts.

[marchy]

@fabiocav this would be fantastic news. Great to have our dev pipe unblocked after 2+ months of not being able to deploy anything from our main-line branch (which we've long upgraded to .NET Core 3.0 on our local machines)

🤞all goes smoothly

[vinay-chaudhari]

@timheuer @bradygaster thanks for help... finally solved my linux deployment issues. There were two problems - first one regarding reading configuration, mine was old code migrated over versions where configuration was manually read fron json, environment variables etc except code reading environment variables was using APPSETTINGS_ prefix. This was the reason, it was missing override of ports via ASPNETCORE_URLS env variable from startup script. Second issue was UseHttpsRedirection which failed because only http port binding was givenfor kestrel. I hope that Microsoft documents how Azure App Service hosting on linux is set up - at least I was unable to find it. The most surprising thing is how the same code was running on .net core 2.2.

[ozkank]

Is there any updates related this issue?

[optiks]

Is there any updates related this issue?

Azure Functions 3 + .NET Core 3.1 are now GA. What update are you hoping for?

[jflieben]

@fabiocav @timheuer deployment center doesn't seem to be able to pull 3.1 core apps from git yet even with the 3.1 extension installed, any update / instruction on that?

[fabiocav]

@jflieben updates for that have been provided here: #129 (comment)

[wadepickett]

Hi, any updates for this open issue?
The .NET 3.1 SDK is supported in North Central US and West Central US so far correct? Everywhere else it is .NET SDK 2.2?

[mattwoberts]

FYI, we migrated to azure pipeline deployments which means were no longer dependent in this issue. It was pretty straight forward in the end. Maybe that will work for you?

On Tue, 28 Jan 2020 at 18:59, Wade Pickett ***@***.***> wrote: Hi, any updates for this open issue? The .NET 3.1 SDK is supported in only North Cetnral US and West Central US only <https://aspnetcoreon.azurewebsites.net/> so far correct? Everywhere else it is only .NET SDK 2.2? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#118?email_source=notifications&email_token=AAA2VDBOZWGR36IL3CRWW3TRAB6BPA5CNFSM4I5R7NKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKEPT6I#issuecomment-579402233>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA2VDDJXPAOGT5LG5W4NMLRAB6BPANCNFSM4I5R7NKA> .

-- Matt Roberts e: roberts.mattroberts@gmail.com t: mattwoberts

[wadepickett]

Thanks for the info! Honestly I'm not sure yet if that will help me.

[gulbanana]

it seems that the 3.x sdk is now available in two north american regions, but nowhere else

[FesterCluck]

DAY 60 of Azure Latest (.Net Core 2.2) UNSUPPORTED

With all due respect can we please get an honest update on this issue, along with some timelines? Most of the Azure infrastructure is latest on a deprecated version of .Net Core (2.2). I understand that .Net and Azure do not necessarily release in parity, but the amount of productivity lost due to all the issues regarding education, deployment, virtual asset creation (temp instances.... ugh), and seemingly no warning from Azure or the .Net team about the problems, just "Hey, hurry up and migrate".

If we cannot be provided the sort of updates and transparency we've come to expect from Microsoft via this forum, please provide the appropriate venue.

[AartBluestoke]

@fabiocav is it still a supported action to use an .net core 2.2 of .net core in azure functions, or is deploying.net core functions with "latest" in Australia an unsupported action?

@FesterCluck "NET Core 2.1 will be supported until August 2021 (it is also an LTS release)." -- it seems the supported action may be to downgrade to 2.1 ...

[eflorespalma]

I need to use net core 2.2 and it doesnt appear. It's an App Service in Linux

[glloyd2010f]

When deploying from an Azure DevOps Pipeline to a Function App on Linux , how are we supposed to target the 3.X Version with the Azure App Service deploy task?? From I have gathered the only two options are .NET (dotnet core 2.0) and JavaScript (Node).

[timheuer]

@glloyd2010f this is what i have:

[kuttikrishnan]

I have a web application built on top of Asp.net core 2.1 Web API , Angular, Azure SQL Server DB, Entity Framework 2.1.4 . The application is hosted it in the Azure AppService (please assume the URL as “abctest.azurewebsites.net”) . Also I have configured a custom domain (will call it as “abctest.com”).
The application is working fine with out any issue .

I tried to Migrate this “.net core 2.1” Web API to “.net core 3.1” . Also I upgrade my EF version from “2.1.4” to “2.2.6” . Everything works fine in the local environment . But after I published this build to my Azure App service , I am facing some issues as mentioned below .
The API is having some latency to return the result after updating an records

• This is happening only when I am using the custom domain end point “abctest.com”. But it is not throwing any error, instead it is fetching the old record (just before the update).
• Even I have checked the DBs call through the profiler, and there I am not able to find those DB calls . But after some 2-3 minutes , I am getting those records and able to see the DB calls through the profiler.
• Also I have checked the “request” through the application insights , when I am getting the old records I am not able to find the request logs there. That looks like, it is not even hitting my Azure app service site from the custom domain.
• Even we tried to roll back the framework to “.net core 2.1” and still it works fine with the same AppService and custom domain.

This issue is not happening with the direct azure website URL (“abctest.azurewebsites.net”) :It is working fine without any issue .
But when the application was running in “.net Core 2.1” , it was working fine with both Azure site URL and custom domain URL.

It will be very helpful if some one able to help to figure out the issue here.

[bradygaster]

@kuttikrishnan - presuming you're publishing from VS, could you check the "delete all files" checkbox to force deletion of all the files currently on the machine.

[kuttikrishnan]

@bradygaster , I am not directly publishing from VS . We are using Octopus and Jenkins for that . In this case also , it is published by Octopus.

[bradygaster]

@kuttikrishnan can you stop the site manually, delete the files, then re-publish? Whilst the mechanic I mentioned is specific to VS, one can do it without VS, too.