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

[drapadubok]

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.

[monty-dev]

We had this same exact issue when deploying to the West US region today. In fact, all of our deployed functions disappeared. The function apps remained, but the functions were gone. Could not deploy and saw your same issue above.

The workaround was deleting the function apps and redeploying to East US, the only other alternative in USA that supports consumption linux at the moment. Very troubling issue.

[drapadubok]

I talked with Azure support and for me using the service plan instead of consumption plan made the thing work, but it's not really a solution of the issue, rather a work around.

[balag0]

@drapadubok Thanks for reporting this. We did have an issue in West Us and West Europe yesterday which has since been fixed.
Your existing apps should continue to work again now. Please let us know if you are still seeing any issues.

[drapadubok]

Seems like this is not a relevant issue anymore, good that it was fixed.

[j08lue]

Same hickup today in West Europe. East US works.

[crgarcia12]

Same here, I am getting hit at the moment

[calinarens]

Same hickup today in West Europe

[issacnitin]

Same hickup today in West Europe

In West US as well

[uoldfield]

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...

[uoldfield]

App Service Plan works over the Consumption Plan - we're using the B1 tier for Dev/Test.

[panakouris]

Same issue here. (East US)

[andres-ivadolabs]

Same issue here (east us)

[panakouris]

Today I tried to deploy my app to the West and East US regions. At the end deploying to West Europe region worked for me

[fernandrez]

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

[j08lue]

@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?

[Shunderpooch]

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

[jackmawer]

Having this today too.

[bigdatamoore]

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.

[ericdrobinson]

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...

[JK87iab]

Same issue as well Error calling sync triggers (BadRequest). and cant see the functions

[blaw2422]

Same here, just trying to bump counts on this issue so they can fix it

[crgarcia12]

Same here, just trying to bump counts on this issue so they can fix it

This one is closed, please vote in this one:
https://github.com/Azure/azure-functions-core-tools/issues/1130

[lucasasterio25]

I'm trying deploy app functions and get this error: Error calling sync triggers (Unauthorized).

my function (aztrial) is not deployed

[wasuaje]

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).

[WumpusOverlord]

Having the same issue in West Europe:

Deployment completed successfully.
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Error calling sync triggers (BadRequest).

[MariusFearn]

Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Error calling sync triggers (Unauthorized).

same problem 29/05/2019

[dmitrysmirnovfinnair]

Same here, interleaved with Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Syncing triggers...
Syncing triggers...
Response status code does not indicate success: 408 (Request Timeout).

[friaN7331]

Uploading 3,86 MB [###############################################################################]
Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Syncing triggers...
Error calling sync triggers (BadRequest).

Same here 11/06/2019

[SacredSkull]

I've found that going into the portal and stopping the function, then publishing allows the syncing to complete... but it still doesn't deploy correctly and shows no functions available :(

[divyagandhisethi]

Can you please share your app name?

[mebibou]

Personally I'm just having some timeouts today:

Uploading 85.45 MB []Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Response status code does not indicate success: 408 (Request Timeout).

Used to work fine before, this whole thing is just highly unstable

[divyagandhisethi]

@mebibou - Can you share your app name?

[SacredSkull]

I cannot share the app name for... reasons... but I can tell you that as soon as I moved to a different region the issues disappeared - this seems to be really specific to certain regions.

[mebibou]

@divyagandhii This is happening in East US with app service plan EastUSLinuxDynamicPlan on 2 different Function Apps, so probably a region problem yeah

[bigdatamoore]

We are experiencing the same issues using function core tools to publish to the East US region. West US region is working fine.

[divyagandhisethi]

We are looking into this.

[bigdatamoore]

According to Microsoft, there is a new functions runtime that is being released that has a fix for this. https://github.com/Azure/azure-functions-host/releases/tag/v2.0.12575

[anirudhgarg]

For this particular issue as @bigdatamoore pointed out we are fixing this is in the host and will be rolled out in the next day or two.This issue which is closed is being used for many unrelated root causes and thus is difficult to monitor/change status on etc. So I am going to lock this. Please open new issues if you see a repeat of this behavior