-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux: Unable to access <app>.scm.azurewebsites.net, Service Unavailable #1173
Comments
I see the app was created with an explicit server farm. For (linux) consumption apps the serverfarm should have been empty when created through the portal. There shouldn't have been an option to specify a server farm / app service plan in the portal. Are you seeing something else when you create a consumption linux function app using the portal? |
Mine looks like yours in the portal. You may be looking at the one created from Visual studio publish tool. I made a few :) |
Thanks. I am looking at the site named bddev. If you were creating a linux consumption function app (based on the screenshot) those sites do not have scm sites (and do not support zip deploy) I can see the documentation is not clear about this. I opened an issue to fix the docs. - MicrosoftDocs/azure-docs#28809 For the site bddev , the site create request included an explicit app service plan. For consumption apps this property should have been empty and this is what i am seeing too when i tried to create a site from the portal. In fact from the above screen shot you can see there is no option to even select an app service plan. so i am trying to understand what was different in your create workflow to see if there is may be a bug somewhere. |
As for the Run as Package, are you referring to https://docs.microsoft.com/en-us/azure/azure-functions/run-functions-from-deployment-package ? How do I package? Do I just do the msbuild publish action like I would a website and zip that up? I'll give it a shot. |
I am not seeing any errors with the apps i tested with earlier. for this particular app, some how the app has gotten into an inconsistent state which i couldn't repro myself, hence my earlier questions on your create flow :) Yes, that is the high level description of how Run-From-Package works. You can use Functions core tools ( https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function-azure-cli-linux#deploy-the-function-app-project-to-azure) or Both the tools also support creating new function apps. Let us know if you have any other questions. |
Thanks-- I tried in US East and wasn't even able to do so. You can see the JSON response from the request in the SR ticket. I'll try again later this weekend. The folks at Azure Support were able to reproduce. |
I was able to locate the bug and the fix should be deployed with the next release. Let me know if you are having trouble deploying with functions core tools / vs code. |
Thanks. When is the next release? |
It should be complete in another week. I will update this thread once it is complete. |
Closing this as resolved. Please let us know if you continue to see this issue. |
The same happened to me. I also deleted and redeployed apps with the same name multiple times.
I just created a new linux/consumption function app and got the following while attempting to deploy from VS2019:
The attempt to publish the ZIP file through https://bddev.scm.azurewebsites.net/api/zipdeploy failed with HTTP status code ServiceUnavailable.
I created the function app via the publish wizard.
The same happened when I created a Linux/consumption function app via the Azure Portal directly. Azure Support was able to reproduce (see SR # 119040321001449) and directed me to make an issue here.
Note: I initially commented on projectkudu/kudu#2804.
The text was updated successfully, but these errors were encountered: