rjgoyln opened a new pull request, #11781: URL: https://github.com/apache/ozone/pull/11781
## What changes were proposed in this pull request? Under Kerberos, `UserInfo.userName` is the full principal (`[email protected]`), while the user table is keyed by the volume owner's short name (`alice`). Tenant create read the owner's volume list under the principal, found none, and its response then replaced the owner's row with only the tenant volume: - the owner's earlier volumes disappear from `ozone sh volume list`; - once that row is emptied, deleting or re-owning a dropped volume fails with `USER_NOT_FOUND`. Multi-tenancy requires Kerberos, so every tenant create is affected. The owner now comes from the `VolumeInfo` built in `preExecute`, as in `OMVolumeCreateRequest`; this is the JIRA patch's fix. Rows already truncated are not repaired. The change is in the apply step, so during a rolling upgrade an OM still on the old version keeps writing the truncated row. ## What is the link to the Apache JIRA? https://issues.apache.org/jira/browse/HDDS-17237 ## How was this patch tested? - The new `TestOMTenantCreateRequest` case fails on master with a principal in `UserInfo` and passes with a short name. - Tenant, multi-tenant manager, S3 secret and volume request/response suites pass (72 tests). Generated-by: Claude Code (Opus 5.5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
