Repository navigation
Conversation
Under Kerberos the request's UserInfo carries the full principal while the volume owner and every other user table writer use the short name, so tenant create read an empty list under the principal and the flush replaced the owner's real list with just the tenant volume.
smengcl
marked this pull request as ready for review
October 27, 2026 04:41
echonesis
approved these changes
Oct 27, 2026
Reading the owner's list under the principal also undercounted it in the per-user volume limit check, so a capped owner could still create a tenant.
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
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.
What changes were proposed in this pull request?
Under Kerberos,
UserInfo.userNamecontains the full principal (e.g.alice@EXAMPLE.COM), while the user table is keyed by the owner's short name (alice). Tenant create therefore reads an empty volume list and overwrites the owner's existing list with only the tenant volume.This causes existing volumes to disappear from
ozone sh volume listand can make subsequent volume deletion or ownership changes fail withUSER_NOT_FOUND.The fix uses the owner from
VolumeInfo, built inpreExecute, consistent withOMVolumeCreateRequest.Existing truncated rows are not repaired. During a rolling upgrade, OMs still running the old version can continue to cause this issue.
What is the link to the Apache JIRA?
https://issues.apache.org/jira/browse/HDDS-17237
How was this patch tested?
Generated-by: Claude Code (Opus 5.5)