Application Error when trying to view "https://infoasst-enrichmentweb-gdkis.azurewebsites.net/"web page

[JMS206]

Bug Details

Describe the bug
After deployment step, the web app page displays "Application Error."

** Error Message
Diagnose and Solve Problem Error:
Container infoasst-enrichmentweb-gdkis_0_97335d0f for site infoasst-enrichmentweb-gdkis has exited, failing site start

Secondary Error message after some research:
│ Error: retrieving Account (Subscription: "0bb0eaa9-564e-4f83-8faa-e15d08d445a5"
│ Resource Group Name: "infoasst-hhsworkspace"
│ Account Name: "infoasst-aoai-gdkis"): unexpected status 503 with response: no healthy upstream
│
│ with module.openaiServices.azurerm_cognitive_account.account[0],
│ on core/ai/openaiservices/openaiservices.tf line 1, in resource "azurerm_cognitive_account" "account":
│ 1: resource "azurerm_cognitive_account" "account" {

Steps To Reproduce

1. Click on web app page to test UI.

2. Application Error screen is displayed. Click on "Diagnostic Resources"

3. Diagnose and Solve Problems shows Platform log errors - "Container infoasst-enrichmentweb-gdkis_0_97335d0f for site infoasst-enrichmentweb-gdkis has exited, failing site start"

4. From the web page Deployment Center, view logs: "Failed on Tuesday, May 14"

What is the expected behavior?
I can view the Info Assist web page.

Screenshots

Add any other context about the problem here.

If the bug is confirmed, would you be willing to submit a PR?

• Yes
• No

[dayland]

@JMS206 , It appears your deployment "Oryx" build did not succeed... please go into the Azure Portal for your webapp and select Deployment > Deployment Center from the left ribbon. Then select the Logs tab. If you see the latest deployment logs show a failed state.. then go back to VSCode and run make deploy-webapp again. This will re-run the Oryx build for the website. Once successful try to launch the website again.

There is an ongoing issue where these Oryx builds randomly fail from time to time that we have an open Support case on. For now use the workaround above and we will update the community once we have a more permanent fix.