Skip to content

Azure File Mounting failures not treated as fatal even if App is not using Run-From-Package #9663

@balag0

Description

@balag0

// wawseas
FunctionsLogs
| where PreciseTimeStamp >= datetime(2023-10-11T14:08:29.803Z) and PreciseTimeStamp <= datetime(2023-10-11T14:08:44.804Z)
| where SourceNamespace == "SFLWAWS"
| where RoleInstance == "App-4E21DB8D-638326191442476902"

Repro steps:
Linux Consumption app
No WEBSITE_RUN_FROM_PACKAGE appsetting configured
No remote build triggered,
Configure AzureFiles using WEBSITE_CONTENTAZUREFILECONNECTIONSTRING, WEBSITE_CONTENTSHARE - BUT use invalid account credentials so mounting AzureFiles will fail at runtime.
Trigger cold start

Expected: Instance should cold start and be removed right away since AzureFiles mount failed and the app has no other source of app content.
Actual: Instance continues to stay alive with 0 functions.

Potential Fix:
https://github.com/Azure/azure-functions-host/blob/dev/src/WebJobs.Script.WebHost/Management/AtlasInstanceManager.cs#L310C20-L310C89
The return value from mount operation is ignored here

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions