github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #12306] issue: Remaining split brain issue with group membership changes #16545

New Issue
Closed
opened 2026-04-19 22:26:29 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 22:26:29 -05:00
Owner
Copy Link

Originally created by @Ithanil on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12306

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Other

Open WebUI Version

0.6.0

Ollama Version (if applicable)

No response

Operating System

Debian 12, Docker, Patroni-PostgreSQL+Redis Sentinel

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

All setting changes should be synced between all replicas, without requiring container restarts.

Actual Behavior

Similar to the fixed https://github.com/open-webui/open-webui/issues/10365 and https://github.com/open-webui/open-webui/issues/10278, I still see an equivalent issue with just a particular setting change, namely adding user to groups manually. After adding a user to a group and not restarting all replicas, you may later hit a different replica where the user is not added to the group.

Steps to Reproduce

  1. Create a group
  2. add a user to the group via UI and save
  3. make sure you somehow get connected to a different replica
  4. see the new group exists, but the user is not added to the group there

Restarting all containers directly after the change seems to make the change persistent.

Logs & Screenshots

I don't see related error messages in the log.

Additional Information

While recent code changes have fixed similar issues for other settings, this one appears to remain.

Originally created by @Ithanil on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/12306 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Other ### Open WebUI Version 0.6.0 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12, Docker, Patroni-PostgreSQL+Redis Sentinel ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior All setting changes should be synced between all replicas, without requiring container restarts. ### Actual Behavior Similar to the fixed https://github.com/open-webui/open-webui/issues/10365 and https://github.com/open-webui/open-webui/issues/10278, I still see an equivalent issue with just a particular setting change, namely adding user to groups manually. After adding a user to a group and not restarting all replicas, you may later hit a different replica where the user is not added to the group. ### Steps to Reproduce 1. Create a group 2. add a user to the group via UI and *save* 3. make sure you somehow get connected to a different replica 4. see the new group exists, but the user is not added to the group there Restarting all containers directly after the change seems to make the change persistent. ### Logs & Screenshots I don't see related error messages in the log. ### Additional Information While recent code changes have fixed similar issues for other settings, this one appears to remain.
GiteaMirror added the bug label 2026-04-19 22:26:29 -05:00
GiteaMirror commented 2026-04-19 22:26:30 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 3, 2025):

This seems very unlikely to be caused by multi-replica setup.

This is the endpoint used to retrieve group information: 04799f1f95/backend/open_webui/routers/groups.py (L33)

All group data is stored in the database unlike app.state variables from the previous issue https://github.com/open-webui/open-webui/issues/10365

<!-- gh-comment-id:2774142556 --> @tjbck commented on GitHub (Apr 3, 2025): This seems very unlikely to be caused by multi-replica setup. This is the endpoint used to retrieve group information: https://github.com/open-webui/open-webui/blob/04799f1f95f958674d35ba4854ef62754a4d332e/backend/open_webui/routers/groups.py#L33 All group data is stored in the database unlike app.state variables from the previous issue https://github.com/open-webui/open-webui/issues/10365
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 bug
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#16545
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?