RANGER-5714 : Ranger server returns an incorrect error message when when an admin tries to revoke a non-existing role from a user - #1124
Open
akash-gupta2813 wants to merge 1 commit into
Conversation
…n admin tries to revoke a non-existing role from a user
akash-gupta2813
marked this pull request as ready for review
August 4, 2026 11:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ranger server returns an incorrect error message when when an admin tries to revoke a non-existing role from a user
What changes were proposed in this pull request?
We found the Ranger server would return an incorrect error message when an admin tries to revoke a non-existing role from a user. In what follows I provide the steps to reproduce the issue in a beeline instance connected to Hive Server2.
correct message should be - "Role with name: " + name + " does not exist."
corresponding JIRA issue number. (https://issues.apache.org/jira/projects/RANGER/issues/RANGER-5714)
How was this patch tested?
tested first in deployment with Docker.
then cluster was created and tested with HS2 beeline.