issue: Previously Configured Tool Servers via UI Break When TOOL_SERVER_CONNECTIONS Is Introduced or Empty #21629
Replies: 3 comments 1 reply
-
|
@Classic298 are you able to reproduce? Unable to reproduce from our end, and working as intended. |
Beta Was this translation helpful? Give feedback.
-
|
cannot repro |
Beta Was this translation helpful? Give feedback.
-
|
I'm able to reproduce this. I've observed this when upgrading from pre-0.8.3 to 0.8.3, and thought it was a fluke, so I had to delete and re-add all my existing external tools. Now I just upgraded from 0.8.3 to 0.8.5, and it happened again. I know tool server config are (also) stored in Redis using the This is the log when the pod starts up: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Check Existing Issues
Installation Method
Other
Open WebUI Version
v0.8.3
Ollama Version (if applicable)
No response
Operating System
Red Hat Enterprise Linux CoreOS
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When upgrading or migrating from an older version of Open WebUI where tool servers were configured via the UI and stored in the database, the system should continue to work after the upgrade/migration. All previously configured tool servers should remain available and function correctly, even if a new environment variable TOOL_SERVER_CONNECTIONS is available. The system should handle the presence of old tool server configuration data gracefully, and should not crash or become unusable due to configuration method changes during migration. Tool servers previously managed through the UI should be available in chats and the application UI without requiring manual intervention or data cleanup.
Actual Behavior
After migrating from an older version where tool servers were configured via the UI and stored in the database, the application fails to load these tool servers correctly with the new environment variable TOOL_SERVER_CONNECTIONS bot configured with a placeholder. This results in errors such as IndexError when attempting to access the tools, leading to the complete unavailability of previously configured tools in both the application UI and in new chats. As a result, users are unable to access or use any of the existing tools within new or ongoing chats, effectively breaking key functionality after the upgrade.
Steps to Reproduce
Logs & Screenshots
File "/app/backend/open_webui/routers/tools.py", line 81, in get_tools
connection = request.app.state.config.TOOL_SERVER_CONNECTIONS[
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
IndexError: list index out of range
Additional Information
No response
Beta Was this translation helpful? Give feedback.
All reactions