Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specified scale type 'Standard' of account deployment is not supported by GPT4 or GPT35TURBO #52

Open
sivi3883 opened this issue Oct 10, 2023 · 2 comments

Comments

@sivi3883
Copy link

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

When deploying End_to_end_Solutions
AOAISearchDemo application, I ran with the below issue when I ran azd up command after following the steps of starting from the scratch -"https://github.com/Azure-Samples/openai/tree/main/End_to_end_Solutions/AOAISearchDemo#starting-from-scratch"

The template deployment 'openai' is not valid according to the validation procedure.
The specified scale type 'Standard' of account deployment is not supported by the model

I tried with both gpt35turbo and gpt4. Please let me how to fix this deployment error

Every resource except openai got deployed successfully

Any log messages given by the failure

Expected/desired behavior

The application should get deployed successfully on Azure infrastructure. Once the app is up, I should be able to query the application.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Window10

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

@cmw2
Copy link

cmw2 commented Oct 30, 2023

I hit the same thing. I got around it by changing the accounts/deployments bicep (in infra/core/ai/cognitiveservices.bicep) to use a newer version of the api, and setting sku instead of scaleSettings. Not 100% sure this is right, but I got this by manually deploying a model and then generating bicep from it. (I hardcoded values while I play with things but they should probably be parameters.)

@batchSize(1)
resource deployment 'Microsoft.CognitiveServices/accounts/deployments@2023-05-01' = [for deployment in deployments: {
  parent: account
  name: deployment.name
  sku: {
    name: 'Standard'
    capacity: 40
  }
  properties: {
    model: deployment.model
    raiPolicyName: contains(deployment, 'raiPolicyName') ? deployment.raiPolicyName : null
    // scaleSettings: deployment.scaleSettings
  }
}]

@stateofthearb
Copy link

I hit the same thing. I got around it by changing the accounts/deployments bicep (in infra/core/ai/cognitiveservices.bicep) to use a newer version of the api, and setting sku instead of scaleSettings. Not 100% sure this is right, but I got this by manually deploying a model and then generating bicep from it. (I hardcoded values while I play with things but they should probably be parameters.)

@batchSize(1)
resource deployment 'Microsoft.CognitiveServices/accounts/deployments@2023-05-01' = [for deployment in deployments: {
  parent: account
  name: deployment.name
  sku: {
    name: 'Standard'
    capacity: 40
  }
  properties: {
    model: deployment.model
    raiPolicyName: contains(deployment, 'raiPolicyName') ? deployment.raiPolicyName : null
    // scaleSettings: deployment.scaleSettings
  }
}]

Thank you! That worked like a charm!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants