Description:
I am experiencing an issue with the one-click deployment from the Azure OpenAI Studio (Chat Playground). The web app is being deployed with the following settings:
- Web App Plan: S1
- Region: Sweden Central
The deployment process completes successfully, but the web app fails to start. I have tried deploying with and without the "enable history" feature, but the issue persists.
Upon reviewing the logs, the following errors are consistently shown:
-
ModuleNotFoundError: No module named 'app'
-
Worker exited with code 3
and [ERROR] Shutting down: Master
-
Container didn't respond to HTTP pings on port: 8000, failing site start
As this is a one-click deployment, I expect it to work out of the box. However, it seems there is a problem related to the application startup, potentially due to a misconfiguration in the deployed container or missing files. I need assistance in resolving this issue as soon as possible.
Steps Taken:
- Tried deploying both with and without the "enable history" feature.
- Checked the logs, which indicate a failure during startup.
Please advise on the necessary steps or configuration changes required to resolve this issue.Description:
I am experiencing an issue with the one-click deployment from the Azure OpenAI Studio (Chat Playground). The web app is being deployed with the following settings:
- Web App Plan: S1
- Region: Sweden Central
The deployment process completes successfully, but the web app fails to start. I have tried deploying with and without the "enable history" feature, but the issue persists.
Upon reviewing the logs, the following errors are consistently shown:
-
ModuleNotFoundError: No module named 'app'
-
Worker exited with code 3
and [ERROR] Shutting down: Master
-
Container didn't respond to HTTP pings on port: 8000, failing site start
As this is a one-click deployment, I expect it to work out of the box. However, it seems there is a problem related to the application startup, potentially due to a misconfiguration in the deployed container or missing files. I need assistance in resolving this issue as soon as possible.
Steps Taken:
- Tried deploying both with and without the "enable history" feature.
- Checked the logs, which indicate a failure during startup.
Please advise on the necessary steps or configuration changes required to resolve this issue.