Azure / Azure/azure-functions-host
Host should fail gracefully if mounting file system fails in Linux Dedicated
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 483
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
Today if the mounting of a file system fails or times out, the host sees an error No such device : '/home/LogFiles/Application/Functions/Host' after attempting to restart multiple times. This error can be handled more gracefully instead of abruptly failing to point to the issue being with the fileshare mounting.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Linux Dedicated failure when the file-system mount times out or fails, then trace how repeated host restarts surface the No such device error for /home/LogFiles/Application/Functions/Host. Done means the host reports the file-share mounting problem clearly instead of failing abruptly; the issue names no files or tests to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100