-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: [privilege_group] The error message is not helpful when adding the valid privilege to the not exist privilege group #37843
Comments
And the same if adding the invalid privilege to the exist privilege group:
|
And this issue exists in interface "remove_privileges_from_group":
|
/assign @shaoting-huang |
@yanliang567: GitHub didn't allow me to assign the following users: shaoting-huang. Note that only milvus-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
And when add/remove privileges to built-in privilege group, it report error:
results:
expect: |
issue: #37031 also fix issues: #37843, #37842, #37887 Signed-off-by: shaoting-huang <[email protected]>
after fix:
|
Fixed:
|
Not Fixed:
|
|
Verified and fixed in latest dev image:
|
Close it first, and will reopen it if there are any errors on the master image when the fix pr is merged. |
issue: milvus-io#37031 also fix issues: milvus-io#37843, milvus-io#37842, milvus-io#37887 Signed-off-by: shaoting-huang <[email protected]>
Is there an existing issue for this?
Environment
Current Behavior
The error message is not helpful when adding the valid privilege to the not exist privilege group
Expected Behavior
report errors like "not exist privilege group"
Steps To Reproduce
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: