azure-functions-core-tools: Error calling sync triggers (BadRequest). Python runtime on Linux.

I’m trying to get the basic tutorial example working, using python 3.6.5, planning to have it on Linux platform. Here is the approach:

az group create --name testResourceGroup123 --location westeurope
az storage account create --name teststorageff --resource-group testResourceGroup123 --location westeurope --sku Standard_LRS

func init testFuncApp --worker-runtime python
func new --name TestFunc --language python --template HTTPTrigger

az functionapp create --resource-group testResourceGroup123 --os-type Linux \
--consumption-plan-location westeurope --runtime python \
--name testFuncAppff --storage-account teststorageff

func azure functionapp publish testFuncAppff

Trying this results in:

Preparing archive...
Uploading 74.01 MB [##############################################################################]
Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Error calling sync triggers (BadRequest).

When I go to portal and try to check the URL on the function app, I get The service is unavailable.

The function is not deployed in the end. I would be grateful for any ideas or advices.

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 3
Comments: 38 (1 by maintainers)

Most upvoted comments

Same hickup today in West Europe

calinarens on Feb 7, 2019

We were having this same issue yesterday (3/19/2019) around 16:00 EST.

still having the same issue today as well (3/20/2019). Not able to deploy to EastUS. WestUS is working.

bigdatamoore on Mar 20, 2019

Having this today too.

jackmawer on Mar 20, 2019

We’ve been experiencing this as well.

It sounds like this is a service-side issue. I would like to request that the error reported to the user be adjusted to include some extra information. The current error:

Error calling sync triggers (BadRequest)

is extraordinarily unhelpful…

ericdrobinson on Mar 20, 2019

Still having this issue WEST EUROPE

Preparing archive… 2019-04-01T16:26:01.7273104Z Uploading 54.49 MB []Upload completed successfully. 2019-04-01T16:26:01.7277142Z Deployment completed successfully. 2019-04-01T16:26:06.7386311Z Syncing triggers… 2019-04-01T16:26:28.1347491Z Syncing triggers… 2019-04-01T16:26:34.5146099Z Syncing triggers… 2019-04-01T16:26:40.7991185Z Syncing triggers… 2019-04-01T16:26:48.2132922Z Syncing triggers… 2019-04-01T16:26:55.0228137Z Syncing triggers… 2019-04-01T16:27:00.7320674Z Error calling sync triggers (BadRequest).

wasuaje on Apr 1, 2019

Same thing happened to us in East US today. Switching to an App Service plan for now until the Python Functions runtime go GA.

Shunderpooch on Mar 19, 2019

@fernandrez - this is just some old thread. Don’t think anyone reads this anyways. 😕

We contacted Azure support for this and got the following response:

There have been some availability issues with Linux apps in the consumption plan which uses Service Fabric Mesh, which is why you were facing issues during deployment. Being in preview such issues can arise before it has General Availability.

I sincerely apologize for the inconvenience you had to face. I totally understand the need to have the services always available and we strive to achieve that on Azure.

I would request you to use the following link for any direct feedback you may have for our Product Group Azure Web App Feedback From my experience, we use your suggestions/feedbacks a LOT to drive improvements in our platform.

You can also use the following GitHub link for more information about Azure Functions on Linux. https://github.com/Azure/Azure-Functions/wiki/Azure-Functions-on-Linux-Preview

So maybe everyone experiencing this should write/upvote some feedback entries?

j08lue on Feb 12, 2019

Why is this closed? This is still happening consistently to me every week or so, westeurope and eastus alike.

fernandrez on Feb 12, 2019

We’re having to build redundancy into our function by deploying it to multiple regions (West Europe, East and West US) and handling duplication of data elsewhere. Despite that, all the regions listed are unavailable for deployment at the moment…

UstDoesTech on Feb 7, 2019