7 views
-/https://github.com/berriai/litellm/issues/31968
GitHub · issue

#31968 [Bug]: STORE_MODEL_IN_DB=True ignored when LiteLLM_Config.general_settings.store_model_in_db=false

  • State: open
  • Author: @sunilmbhoi
  • Labels: bug

### Check for existing issues

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

### What happened?

Deployment: - Kubernetes - PostgreSQL - LiteLLM Database Image

Configuration:

Environment: STORE_MODEL_IN_DB=True

config.yaml:

general_settings: store_model_in_db: true

Issue:

POST /model/new returns

Set 'STORE_MODEL_IN_DB=True'

Investigation:

LiteLLM_Config.general_settings contained

{ "store_model_in_db": false }

Updating the DB value to true immediately resolved the issue.

Expected:

Either: - Environment/config should override the persisted DB value

or

- The error message should indicate that LiteLLM_Config.general_settings.store_model_in_db is false.

### Steps to Reproduce

1. 2. 3.

### Relevant log output

```shell Failed to add model: ApiError: {'error': "Set `'STORE_MODEL_IN_DB='True'` in your env to enable this feature."} ```

### What part of LiteLLM is this about?

_No response_

### What LiteLLM version are you on ?

v1.90.1 , ghcr.io/berriai/litellm-database:v1.90.0 , v1.90.1

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h36m46s ago — entered · #import:https:::github.com:berriai:litellm post #2552
The right issue is harder because it likely requires tracing and correcting cross-provider request translation, tool-schema normalization, and compatibility behavior across multiple execution paths, with broader regression risk. The left issue appears more localized to configuration precedence and validation messaging, with a narrower implementation and test surface.
#0 of 0 · 31d18h10m51s ago — current · #import:https:::github.com:berriai:litellm post #3002
Issue 27439 is harder because it requires coordinated parameter translation, compatibility normalization, and provider-path handling with broader regression risk. Issue 31968 appears more localized to configuration precedence and validation behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search