azure-functions-core-tools: azure-functions-core-tools@2.7.2628 leading to broken Function App when when trying to publish

Using the azure-functions-core-tools@2.7.2628 Python Function Apps can’t be published. Following command is used to publish the Python Function App: func azure functionapp publish FUNCTION_APP_NAME --python --build remote

The output prints: Writing the artifacts to a squashfs file Failed to retrieve remote build status, please visit https://FUNCTION_APP_NAME.scm.azurewebsites.net/api/deployments Response status code does not indicate success: 500 (Internal Server Error).

The Function App is afterwards left in a broken state. Accessing the URL returns “The Service is unavailable.” and the Function App can’t be deleted due to error message: {"Code":"InternalServerError","Message":null,"Target":null,"Details":[{"Message":null},{"Code":"InternalServerError"},{"ErrorEntity":{"Code":"InternalServerError","Message":null}}],"Innererror":null}

Cannot modify this site because another operation is in progress.

PowerShell Function Apps can be published without any problem.

When downgrading the azure-functions-core-tools to version 2.7.2508, publishing works flawlessly.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 19 (2 by maintainers)

Most upvoted comments

Thanks everyone. We were able to identify the issue. As discussed on this thread the impact is to function apps using Key vault references after deploying with the latest core tools.

We have started deploying a fix which should complete in the next 12 hours. There is no need to update the core tools version you are using. Currently West Europe has been updated.

Next steps If your app is in West Europe:

The app should already be fine. If not please continue with Step 1
Restart the app. This is to make sure your app is running on the latest container with the fix applied.
Check if the app is working now. If not please redeploy the app in case the previous deployment had failed in an inconsistent state. There is no need to update the core tools version you are already using.
If you are still seeing issues, please update the thread with the app name and I will investigate (https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately )

If your app is not in west europe: Please share the app name and I will prioritize those apps. In any case we expect the rollout to complete in the next 12 hours across all regions. I will provide an update when this is complete.

balag0 on Jul 10, 2020

@balag0 As I mentioned it Azure Support was working on it and after we found out that the recent Core Tools version is the case they proceed with cleaning up.

The issue is really reproducible. Spin up a Python Azure Function App, have some Key Vault secret references and then try to publish the Function with Core Tools version 3.0.2630.

What I can say for sure that we did not have app settings and Key Vault secret references with the same name.

dan-leanix on Jul 7, 2020