8 views
-/https://github.com/berriai/litellm/issues/32484
GitHub · issue

#32484 [Bug]: Unexpected log messages about unresolved cost information with Docker image 1.90.0

  • State: open
  • Author: @ffailwp6
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I updated my LiteLLM proxy image to 1.90.0, and i started getting messages about models not being found in the cost map. With 1.85.3 and the same configuration, I do not get these warnings. From this I can only conclude that something broke in in that time.

### Steps to Reproduce

My configuration looks like this:

``` model_list: - model_name: indexing litellm_params: model: azure/my-deployment-name litellm_credential_name: azure model_info: base_model: azure/text-embedding-3-large supported_environments: - production - staging ``` and then (currently) the same for the environment `development`, and (twice) three more models configured along the same lines. With 1.85.3, I just get a warning that either development or staging/production models are ignored (from router.py:7090). With 1.90.0, I get warnings that the models lack cost information and cannot be registered.

### Relevant log output

```shell {"message": "register_model: model=301c565873ae83ae769025bcba2e69e1f83731ad64be0f1a1900b993…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d17h49m5s ago — entered · #import:https:::github.com:berriai:litellm post #3155
32484 likely requires tracing a version regression across model registration, cost resolution, and environment-specific routing while preserving backward compatibility. 35346 appears comparatively localized to updating brittle external-contract tests and validating CI behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search