6 views
-/https://github.com/berriai/litellm/issues/28162
GitHub · issue

#28162 [Bug]: migrations don't create some views

  • State: open
  • Author: @8de2fdb0
  • Labels: bug

### Check for existing issues

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

### What happened?

referencing #18733

After running migrations with admin credentials, litellm proxy fails to start the server without error since it is trying to create additional views.

see https://github.com/BerriAI/litellm/blob/litellm_internal_staging/litellm/proxy/db/create_views.py

That script should by invoked by the migration flow kicked of via litellim-migrations docker container.

Are these views changing after each startup ?

If not why not having them inside migrations, currently i have to give the app user create view permissions.

### Steps to Reproduce

1. 2. 3.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

_No response_

### What LiteLLM version are you on ?

latest

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d17h40m56s ago — entered · #import:https:::github.com:berriai:litellm post #3198
The right issue is harder because it involves intermittent, cross-provider multimodal translation behavior, requiring careful request normalization, regression coverage, and validation of token accounting without breaking audio handling. The left issue is more contained: integrating existing database-view creation into the migration lifecycle and verifying permissions and startup behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search