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

[Bug]: Proxy: period (.) in Azure OpenAI model name causes model info to not be recognized #7868

Open
marty-sullivan opened this issue Jan 19, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@marty-sullivan
Copy link
Contributor

marty-sullivan commented Jan 19, 2025

What happened?

If I configure a model in Azure OpenAI like the following it works fine:

  - model_name: 'openai.gpt-4o'
    litellm_params:
      model: 'azure/gpt-4o-2024-11-20' # 👈 Notice the - instead of . before version
      api_base: 'https://my-endpoin.openai.azure.com/'
      api_version: '2024-12-01-preview'
      api_key: 'my-secret'

However, if I name my model with a . in the model name, pricing and other model info is not automatically discovered by LiteLLM. The UI shows blank / null values for everything and is unable to track usage/cost accurately

  - model_name: 'openai.gpt-4o'
    litellm_params:
      model: 'azure/gpt-4o.2024-11-20' # 👈 Notice the . instead of - before version
      api_base: 'https://my-endpoin.openai.azure.com/'
      api_version: '2024-12-01-preview'
      api_key: 'my-secret'

I even tried setting base_model and that doesn't fix it when there is a . in the model name

EDIT:

I also notice an issue with o1 model in Azure. If I name my model deployment in Azure anything but o1 the model details and pricing are not recognized by LiteLLM proxy config. For example model: azure/o1 works but model: azure/o1-2024-12-17 does not work.

Are you a ML Ops Team?

No

What LiteLLM version are you on ?

1.57.3
1.59.1 (for azure/o1 support)

Twitter / LinkedIn details

No response

@marty-sullivan marty-sullivan added the bug Something isn't working label Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant