Host ID collisions in several functionapps and slots although Environment variable "AzureFunctionsWebHost__hostid" is used in every functionapp and every slot

[ulluoink]

• Timestamp: since we use deployment slots
• Function App version: .net 8 isolated, Runtime version 4
• Region: west europe

Repro steps

1. several FunctionApps in one storage account with two deployment slots each (staging and production)
2. in every functionapp and in each slot we have an environment variable "AzureFunctionsWebHost__hostid" with a unique value (just like documented by microsoft)
3. deploy several FunctionApps to their staging slot
4. switch slot of each function to production
5. Error "A collision for Host ID 'functionsv4x64dotnetisolated8pla' was detected in the configured storage account. For more information, see https://aka.ms/functions-hostid-collision." occurs in several functionapps (either in production or in staging slot). The 'functionsv4x64dotnetisolated8pla' value differs from functionapp to functionapp

Expected behavior

no host id collision errors if the environment variable is used as documented

Documentation we used to address this issue:

https://learn.microsoft.com/en-us/azure/azure-functions/storage-considerations?tabs=azure-cli#override-the-host-id
https://learn.microsoft.com/en-us/azure/azure-functions/errors-diagnostics/diagnostic-events/azfd0004#options-for-addressing-collisions
https://github.com/Azure/azure-functions-host/wiki/Host-IDs#host-id-override

[bhagyshricompany]

Hi @ulluoink Thanks for reporting.please raise request on azure portal.

[ulluoink]

/bot not-stale

[ulluoink]

Hi @ulluoink Thanks for reporting https://learn.microsoft.com/en-us/azure/azure-functions/functions-deployment-slots?tabs=azure-portal please ref this link as per the plan have slot creation. support if still have issue please raise request on azuree portal.Thanks

Do not understand what does that mean?

What do you want us to change in our functionapps?

Have you even read what we are doing? We followed each amd every advice and documentation of microsoft and also the linked doc.

[bhagyshricompany]

Hi @ulluoink Thanks for your patience. will update you on this soon.

[ulluoink]

@bhagyshricompany any update on this?

[zenmiao7]

We faced the same problem. Any updates? @satvu

[mathewc]

A fix for this issue was made a few weeks back #10789. Fix will be part of the next release.

[liliankasem]

Going to close this as a duplicate of #10579 - please follow there for further updates.