Closed hunterjam closed 9 months ago
Hi @hunterjam Thanks for reporting this, a few things, the expected is to provide a better end user error, but the question is: if you wait after 5 minutes you still see the same error, how about 10 minutes? Adding @ruoccofabrizio for awareness, since we are trying to have everything ready by Friday. Thank you! Just trying to determine if this is a temporary issue and document the time the users must wait after deployment. Thank you!
hi @hunterjam please double check you have the models (gpt-35-turbo and text-embedding-ada-002) deployed in your Azure OpenAI resource. By default the deployment name in the app settings is equal to the model name (gpt-35-turbo and text-embedding-ada-002) If you named the deployment in a different way, you should update the app settings to match your deployment names.
@gmndrg : we may want to highlight this in the article as well as in the documentation.
Just as side note: we don't deploy Azure OpenAI Resource or model in the resource as it's currently a gated service with some restrictions. So,it's supposed that you already have access to it for running the solution and you just provide the details of your existing deployment(s) in the settings. It's the only component not deployed by the ARM or the bicep.
Hi @gmndrg and @ruoccofabrizio. Good call out. My deployments were named differently. I deleted the original deployments and created new deployments using the model name. Within the Admin site, Explore Data looks better.
Within the User site, still receiving the same error:
Thanks for the feedback @hunterjam By default,the orchestrator uses the function concept of Azure OpenAI, available only on version 0613 of turbo. Your model is currently on a previous version, which does not expose such functionality. I am writing a documentation note to address it and a parameter in the settings (and ARM/ Bicep) to switch to a LangChain orchestrator when you want to use your model version. In the meanwhile, if you update the version, you should be fine.
[heart] Gia Mondragon reacted to your message:
From: Fabrizio Ruocco @.> Sent: Wednesday, August 23, 2023 8:15:46 PM To: Azure-Samples/azure-search-openai-solution-accelerator @.> Cc: Comment @.***> Subject: Re: [Azure-Samples/azure-search-openai-solution-accelerator] ARM Deploy or Bicep Deploy --- Issue (Issue #27)
Thanks for the feedback @hunterjamhttps://github.com/hunterjam By default,the orchestrator uses the function concept of Azure OpenAI, available only on version 0613 of turbo. Your model is currently on a previous version, which does not expose such functionality. I am writing a documentation note to address it and a parameter in the settings (and ARM/ Bicep) to switch to a LangChain orchestrator when you want to use your model version. In the meanwhile, if you update the version, you should be fine.
— Reply to this email directly, view it on GitHubhttps://github.com/Azure-Samples/azure-search-openai-solution-accelerator/issues/27#issuecomment-1690577825 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALBWI76VIP7UANVP6OAZV3TXWZQHHBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE3DIOJZGQZTEMZQQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRRHA3DGOBYGE2TGONHORZGSZ3HMVZKMY3SMVQXIZI. You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@ruoccofabrizio @gmndrg --- Fantastic. Looks like we are up and running. Thank you both very much for your help.
Thank you, James for reporting this before we go live (awesome!) and Fabri for everything as usual! 😊
From: James Hunter @.> Sent: Wednesday, August 23, 2023 2:30 PM To: Azure-Samples/azure-search-openai-solution-accelerator @.> Cc: Mention @.>; Comment @.> Subject: Re: [Azure-Samples/azure-search-openai-solution-accelerator] ARM Deploy or Bicep Deploy --- Issue (Issue #27)
@ruoccofabriziohttps://github.com/ruoccofabrizio @gmndrghttps://github.com/gmndrg --- Fantastic. Looks like we are up and running. Thank you both very much for your help. image.png (view on web)https://github.com/Azure-Samples/azure-search-openai-solution-accelerator/assets/31451884/114cce5e-8744-47fb-953b-ec18d40e014f
— Reply to this email directly, view it on GitHubhttps://github.com/Azure-Samples/azure-search-openai-solution-accelerator/issues/27#issuecomment-1690594245 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALBWI7Y5CKB2UBZBT2ZOWFLXWZR27BFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE3DIOJZGQZTEMZQQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRRHA3DGOBYGE2TGONHORZGSZ3HMVZKMY3SMVQXIZI. You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
added a note to the README to address this. @gmndrg @aahill: please have a look at it
hi @hunterjam please double check you have the models (gpt-35-turbo and text-embedding-ada-002) deployed in your Azure OpenAI resource. By default the deployment name in the app settings is equal to the model name (gpt-35-turbo and text-embedding-ada-002) If you named the deployment in a different way, you should update the app settings to match your deployment names.
@gmndrg : we may want to highlight this in the article as well as in the documentation.
Thank you so much, @ruoccofabrizio, I added a note too in my branch :) will check to avoid merge issues and double content. :)
@gmndrg @hunterjam @aahill added a note on the orchestration strategy as well. Please have a look at it in the README.
@ruoccofabrizio --- Does this field need to be included in the Environment Variables section for local deployment?
[heart] Gia Mondragon reacted to your message:
From: Fabrizio Ruocco @.> Sent: Friday, August 25, 2023 6:35:05 AM To: Azure-Samples/azure-search-openai-solution-accelerator @.> Cc: Comment @.***> Subject: Re: [Azure-Samples/azure-search-openai-solution-accelerator] ARM Deploy or Bicep Deploy --- Issue (Issue #27)
Closed #27https://github.com/Azure-Samples/azure-search-openai-solution-accelerator/issues/27 as completed.
— Reply to this email directly, view it on GitHubhttps://github.com/Azure-Samples/azure-search-openai-solution-accelerator/issues/27 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALBWI7ZCWIYGYGMPW4HQVA3XXBBRTBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJWGQ4TSNBTGIZTBAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOBWGM4DQMJVGM42O5DSNFTWOZLSUZRWY33TMVSA. You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Versions
Mention any other details that might be useful
Based on the error messaging, the APIs for this solution were not deployed.
I experienced the same issue using the Bicep deployment with Azure CLI.