Deployment of Bring your own Data chatbot from Azure Open AI studio never completes.

Question

I am trying to create an employee handbook chatbot. I am satisfied with the answers that have been provided in the Chat Playground of Azure OpenAI Studio, but when I hit deploy to a new web app, a web app resource is created but it never finishes deploying. The Open AI resource is in South Central US S0 and the webapp is South Central US plan F1.

In the resource activity log it shows that "Update Web app source control configuration" fails and gives the following error:

Repository 'UpdateSiteSourceControl' operation failed with System.TimeoutException: Operation POST https://waws-prod-sn1-217.api.azurewebsites.windows.net/api/settings exceeded 100000ms timeout! at Microsoft.Web.Hosting.Administration.Utilities.WebRequestHelper.<GetResponseAsyncWithTimeout>d__10.MoveNext() in C:__w\1\s\src\Hosting\AdministrationService\Microsoft.Web.Hosting.Administration\Utilities\WebRequestHelper.cs:line 65 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.SiteRepositoryProvider.TrackerContext.<GetResponseAsync>d__41.MoveNext() in C:__w\1\s\src\Hosting\AdministrationService\Microsoft.Web.Hosting.Administration\Providers\SiteRepositoryProvider.cs:line 757 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.SiteRepositoryProvider.<SetSettingsAsync>d__31.MoveNext() in C:__w\1\s\src\Hosting\AdministrationService\Microsoft.Web.Hosting.Administration\Providers\SiteRepositoryProvider.cs:line 350 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.ExternalSiteRepositoryProvider.<UpdateSiteSourceControl>d__5.MoveNext() in C:__w\1\s\src\Hosting\AdministrationService\Microsoft.Web.Hosting.Administration\Providers\ExternalSiteRepositoryProvider.cs:line 78 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.WebCloudController.<>c__DisplayClass378_1.<<UpdateSiteSourceControl>b__1>d.MoveNext() in C:__w\1\s\src\Hosting\AdministrationService\Microsoft.Web.Hosting.Administration\Controllers\WebCloudController.cs:line 11540 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.AsyncHelper.RunSyncTResult at Microsoft.Web.Hosting.Administration.WebCloudController.UpdateSiteSourceControl(String subscriptionName, String webspaceName, String name, SiteSourceControl siteSourceControl) in C:__w\1\s\src\Hosting\AdministrationService\Microsoft.Web.Hosting.Administration\Controllers\WebCloudController.cs:line 11535.

Does anyone have any idea of what I need to do to fix this?

Through further clicking on everything in the Portal, I have found that the container couldn't be started. But I do no know what that means or how to fix it.

Answer 1

@Berry, Kylie Since you have only used the option to deploy to a new webapp all the configuration that is required to setup the app should be taken care of at the backend. For some reason since it fails, I would recommend to retry the same with a different name in a different region and a higher pricing tier other than free. Since free tier comes with basic storage and CPU time, it might not be suitable for some OpenAI deployments.

Other than that, if you have to debug further on what could case an app deployment to fail or timeout you can get more logs and change the configuration to re-run the app. See some of the debugging steps here.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.