[Bug]: Data Loss During Upgrade (with store_model_in_db=true) #14661
Description
What happened?
When upgrading from v1.74.7-stable to v1.76.1-stable, the database migration process modifies the litellm_params field in the LiteLLM_ProxyModelTable. Certain information, such as input_cost_per_token and output_cost_per_token, is lost if their values are set to 0 during the upgrade. This results in errors when accessing the model, such as: "this model isn't mapped yet..... Add it here." To resolve this, I had to manually edit and save each model in the interface to regenerate the missing fields.
Relevant log output
Are you a ML Ops Team?
Yes
What LiteLLM version are you on ?
v1.76.1-stable
Twitter / LinkedIn details
No response