You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Azure Functions to deploy a Python 3.11 function app on Linux environment in Europe West. The function app works flawlessly when running on consumption service plan Y1.
However, when I change this plan to dedicated B1 or premium P0v3, the deployment fails and shows the status error where normally the version of the runtime should be listed. If you click on more details it states the message "Encountered an error (ServiceUnavailable) from host runtime."
If you try make an HTTP request, you get 503 Service Unavailable response.
After switching the service plan back to Y1, the function app functions as before.
We also tried plans B2 and P1v3, to rule out memory issues, but the same issue arises. We really want to be able to activate the "always-on" configuration setting, to get rid of warm up times.
Any solution?
Actual Behavior
No response
Steps to Reproduce
No response
Relevant code being tried
No response
Relevant log output
No response
requirements.txt file
No response
Where are you facing this problem?
Production Environment (explain below)
Function app name
runeasi-testing-python-fnapp
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Expected Behavior
I'm using Azure Functions to deploy a Python 3.11 function app on Linux environment in Europe West. The function app works flawlessly when running on consumption service plan Y1.
However, when I change this plan to dedicated B1 or premium P0v3, the deployment fails and shows the status error where normally the version of the runtime should be listed. If you click on more details it states the message "Encountered an error (ServiceUnavailable) from host runtime."
If you try make an HTTP request, you get 503 Service Unavailable response.
After switching the service plan back to Y1, the function app functions as before.
We also tried plans B2 and P1v3, to rule out memory issues, but the same issue arises. We really want to be able to activate the "always-on" configuration setting, to get rid of warm up times.
Any solution?
Actual Behavior
No response
Steps to Reproduce
No response
Relevant code being tried
No response
Relevant log output
No response
requirements.txt file
No response
Where are you facing this problem?
Production Environment (explain below)
Function app name
runeasi-testing-python-fnapp
Additional Information
No response
The text was updated successfully, but these errors were encountered: