search

Azure / azure-functions-host

The host/runtime that powers Azure Functions
https://functions.azure.com
MIT License
1.92k stars 442 forks source link

Error indexing method ‘functionName’ Method overloads are not supported #8248

Open TsuyoshiUshio opened 2 years ago

TsuyoshiUshio commented 2 years ago

Starting 3/4/2022 - The latest Functions Host release 4.2.1.17812 introduced a defect for a subset of .NET in-proc Function Apps (for apps that more than one function in a class) affecting their Function executions. The error that would be seen is:
Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException : Error indexing method. This issue can be mitigated right now by pinning back to version 4.1.3.17473. The ETA of the rollback completion will be 19:30 PST 3/18/2022.

Customers who are still affected by the issue - following are the mitigations per sku

marnilss commented 2 years ago

I don't see any mitigation for people running Docker Images with tag "mcr.microsoft.com/azure-functions/dotnet:4"

You need to remember us running Function Apps as containers, thus not using PaaS service in Azure Portal.

TsuyoshiUshio commented 2 years ago

Hi @marnilss In your case, You are using App Service Plan, right?

In this case, you might encounter following case. Could you share with me your site name to my e-mail account? (I'll remove the e-mail after you send me an e-mail) 

Linux Dedicated / EP - First Customer has to to portal and restart the application. If that does not mitigate, Let us know.
marnilss commented 2 years ago

Hi @marnilss In your case, You are using App Service Plan, right?

In this case, you might encounter following case. Could you share with me your site name to my e-mail account? (I'll remove the e-mail after you send me an e-mail) 

Linux Dedicated / EP - First Customer has to to portal and restart the application. If that does not mitigate, Let us know.

Hi @TsuyoshiUshio , no I'm not using any Azure Function App at all, I'm running the mentioned Docker image in Kubernetes. (https://docs.microsoft.com/en-us/azure/azure-functions/functions-kubernetes-keda)

TsuyoshiUshio commented 2 years ago

There is several options. I think k8s cluster caches the image.

  1. make imagepullpolicy as always
  2. Use the specific version of the image. e.g. mcr.microsoft.com/azure-functions/dotnet:4.1.3
    You can find the available versions in https://mcr.microsoft.com/v2/azure-functions/dotnet/tags/list

4 is pinned to 4.1.3 already. Could you try one of them?