Azure Function cannot retrieve settings from Azure App Config in West EU

Quan Van Mai 106 Reputation points
2021-01-14T07:31:34.433+00:00

Hi,

We are having some azure functions deployed on Azure (West EU).
Suddenly, none of them can be triggered today (14th January 2021). We are using the Service Bus Queue trigger.
We have two different resource groups in the West EU and all functions in those resource groups do not perform as expected anymore.

After checking the logs in Application Insights, we found a lot of exceptions that indicate our azure functions cannot retrieve the settings from the Azure App Config such as Azure Storage connection string, Queue Name, etc.

Our functions in South East Asia is still working normally.

If you run into this problem like us, please let us know.

Here is a log we have traced: 56516-azure-function-err.txt

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,250 questions
Azure App Configuration
Azure App Configuration
An Azure service that provides hosted, universal storage for Azure app configurations.
208 questions
Accepted answer
  1. Quan Van Mai 106 Reputation points
    2021-01-14T12:07:12.853+00:00

    I have resolved it myself.
    For anyone who encounters the same problem as me, you can opt-out of the automatic upgrade to v3 by setting the FUNCTIONS_EXTENSION_VERSION to ~2.0.

    More information could be found here:
    https://github.com/Azure/azure-functions-host/wiki/Platform-upgrade-from-Azure-Functions-runtime-v2-to-v3#opting-out-of-the-upgrade

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pragna Gopa 1 Reputation point
    2021-01-14T15:32:19+00:00

    Thank you for reporting the issue. Yes, this is related to platform auto-upgrade. More details: https://github.com/Azure/app-service-announcements/issues/266 . We have rolled out upgrade to West Europe 01/13/21. More regions will be upgraded today in the next few days. Please pin your apps ahead of time to avoid disruption. As mentioned in the referenced issue above, we recommend customers to move Functions V3 at your earliest convinience.

    0 comments