[
https://issues.apache.org/jira/browse/HDDS-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen resolved HDDS-16158.
-------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
> Fix sendDeleteKeysRequestAndClearList Authorization and FSO Trash Handling
> --------------------------------------------------------------------------
>
> Key: HDDS-16158
> URL: https://issues.apache.org/jira/browse/HDDS-16158
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Priyesh Karatha
> Assignee: Priyesh Karatha
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> {{sendDeleteKeysRequestAndClearList}} has two related issues that prevent
> delete-key requests from being handled correctly in production, particularly
> when ACLs are enabled and when FSO trash handling is configured.
> First, {{sendDeleteKeysRequestAndClearList}} submits the Ratis request
> without executing {{preExecute}} under the appropriate UGI context. As a
> result, {{userInfo.userName}} remains blank. When ACLs are enabled,
> {{resolveBucketLink}} attempts to create a UGI from the blank user
> information and fails with {{{}UNAUTHORIZED{}}}.
> Second, {{ozoneTrash}} is captured during {{KeyManager}} construction, before
> {{OzoneManager.startTrashEmptier()}} is invoked. Since all {{OzoneManager}}
> startup paths call {{keyManager.start()}} before starting the trash emptier,
> {{ozoneManager.getOzoneTrash()}} is {{null}} when the constructor runs. The
> field is never updated afterward, causing the FSO {{moveToTrash}} path in
> {{handleAndClearFullList}} to remain unreachable in production.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
