Originally created by @jeeteshchel on GitHub (Jan 13, 2025).
Bug Report
Installation Method
Git clone and Docker setup.
Environment
Open WebUI Version: v0.5.4
Ollama (if applicable): N/A
Operating System: Ubuntu 24.04
Browser (if applicable): Chrome 131.0.6778.265
Confirmation:
I have read and followed all the instructions provided in the README.md.
I am on 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 provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
In Model Edit page, user selects a user group from the dropdown and clicks "Save," the following should occur:
The model update API request for model update should include the selected group_id in the `access_control.read.group_ids array.
Upon reopening the model edit page, the previously selected/saved user group name assignment should be listed.
Actual Behavior:
After selecting a user group and clicking "Save," a success response is displayed, however
The API request for model update shows an empty access_control.read.group_ids array.
When the model edit page is reopened, the selected user group is not displayed as assigned.
Description
Bug Summary:
The application fails to update AccessControl component with the selected user group on form submission, resulting in the group assignment not being persisted.
Steps to Reproduce:
Navigate to the model view/edit page in the Open WebUI.
Select a user group from the dropdown menu under the "Groups" section.
Click the "Save & Update" button.
Observe the success message,.
Check the API request payload for the model update. The access_control.read.group_ids array is empty.
Reopen the model edit page and observe that the selected group is not displayed as assigned.
Logs and Screenshots
Additional Information
The issue appears to be related to the front-end failing to properly include the selected group_id in the API request payload.
There is no visible error message indicating why the access_control.read.group_ids array remains empty.
Note
If you need further information or assistance in reproducing the bug, feel free to reach out. Thank you for your attention to this issue!
Originally created by @jeeteshchel on GitHub (Jan 13, 2025).
## Bug Report
## Installation Method
Git clone and Docker setup.
## Environment
- **Open WebUI Version:** v0.5.4
- **Ollama (if applicable):** N/A
- **Operating System:** Ubuntu 24.04
- **Browser (if applicable):** Chrome 131.0.6778.265
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
In Model Edit page, user selects a user group from the dropdown and clicks "Save," the following should occur:
1. The model update API request for model update should include the selected `group_id` in the `access_control.read.group_ids array.
2. Upon reopening the model edit page, the previously selected/saved user group name assignment should be listed.
## Actual Behavior:
1. After selecting a user group and clicking "Save," a success response is displayed, however
2. The API request for model update shows an empty `access_control.read.group_ids` array.
3. When the model edit page is reopened, the selected user group is not displayed as assigned.
## Description
**Bug Summary:**
The application fails to update AccessControl component with the selected user group on form submission, resulting in the group assignment not being persisted.
**Steps to Reproduce:**
1. Navigate to the model view/edit page in the Open WebUI.
2. Select a user group from the dropdown menu under the "Groups" section.
3. Click the "Save & Update" button.
4. Observe the success message,.
5. Check the API request payload for the model update. The `access_control.read.group_ids` array is empty.
6. Reopen the model edit page and observe that the selected group is not displayed as assigned.
## Logs and Screenshots
## Additional Information
- The issue appears to be related to the front-end failing to properly include the selected `group_id` in the API request payload.
- There is no visible error message indicating why the `access_control.read.group_ids` array remains empty.
## Note
If you need further information or assistance in reproducing the bug, feel free to reach out. Thank you for your attention to this issue!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jeeteshchel on GitHub (Jan 13, 2025).
Bug Report
Installation Method
Git clone and Docker setup.
Environment
Confirmation:
Expected Behavior:
In Model Edit page, user selects a user group from the dropdown and clicks "Save," the following should occur:
group_idin the `access_control.read.group_ids array.Actual Behavior:
access_control.read.group_idsarray.Description
Bug Summary:
The application fails to update AccessControl component with the selected user group on form submission, resulting in the group assignment not being persisted.
Steps to Reproduce:
access_control.read.group_idsarray is empty.Logs and Screenshots
Additional Information
group_idin the API request payload.access_control.read.group_idsarray remains empty.Note
If you need further information or assistance in reproducing the bug, feel free to reach out. Thank you for your attention to this issue!
@tjbck commented on GitHub (Jan 13, 2025):
You need to click on the plus button to add.