github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22077] bug:Tool calling broken in v0.8.5; rollback to v0.8.4 no longer works due to tag update #35162

New Issue
Closed
opened 2026-04-25 09:23:26 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 09:23:26 -05:00
Owner
Copy Link

Originally created by @gollon on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22077

Background

  • I originally used open-webui v0.8.4 and tool calling worked normally.
  • Yesterday I upgraded to v0.8.5 and deleted the v0.8.4 image; after the upgrade the Tool/Function calling stopped working.
  • I downloaded v0.8.4 again to roll back, but the Tool still cannot be called.
  • I discovered the current v0.8.4 image/tag is not the same as the original v0.8.4 I had: it appears v0.8.4 was updated recently (same as v0.8.5).

Steps to reproduce

  1. Run v0.8.4 (the original image) — Tool calling works.
  2. Upgrade to v0.8.5 and remove v0.8.4 — Tool calling breaks.
  3. Pull v0.8.4 again — Tool calling still broken; found v0.8.4 was updated recently.

Observed behavior

  • Tool/function calls that worked on the original v0.8.4 are not invoked in v0.8.5.
  • Re-pulling tag v0.8.4 now fetches a different build (recently updated), so rollback to v0.8.4 no longer recovers the old working state.

Expected behavior

  • Tags for released versions (e.g., v0.8.4) should remain immutable (or documented if re-used), allowing reliable rollback.

Additional info you can attach

  • Exact docker image IDs (before/after), e.g. docker images --digests output.
  • Timestamps for when you pulled images.
  • Logs/traces showing tool invocation failure.
  • Platform (docker/podman/k8s), OS, and how you run open-webui.

Impact

  • Breaking ability to roll back to a previously working release.

Suggested mitigation

  • Avoid reusing tags for different builds; publish immutable tags or use digests.
  • Add release notes if tags are force-updated and indicate incompatibilities.
Originally created by @gollon on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22077 Background - I originally used open-webui v0.8.4 and tool calling worked normally. - Yesterday I upgraded to v0.8.5 and deleted the v0.8.4 image; after the upgrade the Tool/Function calling stopped working. - I downloaded v0.8.4 again to roll back, but the Tool still cannot be called. - I discovered the current v0.8.4 image/tag is not the same as the original v0.8.4 I had: it appears v0.8.4 was updated recently (same as v0.8.5). Steps to reproduce 1. Run v0.8.4 (the original image) — Tool calling works. 2. Upgrade to v0.8.5 and remove v0.8.4 — Tool calling breaks. 3. Pull v0.8.4 again — Tool calling still broken; found v0.8.4 was updated recently. Observed behavior - Tool/function calls that worked on the original v0.8.4 are not invoked in v0.8.5. - Re-pulling tag v0.8.4 now fetches a different build (recently updated), so rollback to v0.8.4 no longer recovers the old working state. Expected behavior - Tags for released versions (e.g., v0.8.4) should remain immutable (or documented if re-used), allowing reliable rollback. Additional info you can attach - Exact docker image IDs (before/after), e.g. docker images --digests output. - Timestamps for when you pulled images. - Logs/traces showing tool invocation failure. - Platform (docker/podman/k8s), OS, and how you run open-webui. Impact - Breaking ability to roll back to a previously working release. Suggested mitigation - Avoid reusing tags for different builds; publish immutable tags or use digests. - Add release notes if tags are force-updated and indicate incompatibilities.
GiteaMirror commented 2026-04-25 09:23:27 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Mar 1, 2026):

⚠️ Missing Issue Title Prefix

@gollon, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:3979678995 --> @pr-validator-bot commented on GitHub (Mar 1, 2026): # ⚠️ Missing Issue Title Prefix @gollon, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-04-25 09:23:28 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Mar 1, 2026):

This is the thirteenth duplicate issue

USE THE SEARCH BEFORE OPENING ANOTHER ONE

It is fixed in dev

<!-- gh-comment-id:3979710298 --> @Classic298 commented on GitHub (Mar 1, 2026): This is the thirteenth duplicate issue USE THE SEARCH BEFORE OPENING ANOTHER ONE It is fixed in dev
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#35162
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?