smengcl opened a new pull request, #11599:
URL: https://github.com/apache/ozone/pull/11599

   Generated-by: Claude Code (Opus 5.5)
   
   ## What changes were proposed in this pull request?
   
   `Verify Role-Scoped Token Accesses` in `ozone-secure-sts-multitenant.robot` 
still fails intermittently with `AccessDenied`, now on the linked bucket read 
(`Get Object Should Succeed ${TENANT_ONE_LINKED_BUCKET} 
${ANOTHER_BUCKET_TESTFILE}`).
   
   HDDS-16560 added a `Wait Until Keyword Succeeds` on the first read of the 
test, intended to wait for all role policies to reach the Ranger plugin cache. 
That read only depends on an early policy, though. The linked bucket read needs 
the `${TENANT_TWO} ${TENANT_TWO_ANOTHER_BUCKET} table access` policy, which is 
created last. In the failing run, the leader OM loaded Ranger policy version 70 
at 08:43:48 and version 72 at 08:44:18: the wait passed on version 70, and the 
linked bucket read at 08:44:16 was denied.
   
   This patch waits on the linked bucket read instead. Since it needs the last 
created policy, once it succeeds all earlier policies are in the plugin cache 
as well, and the remaining checks of the access matrix run against a complete 
policy set.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-17099
   
   ## How was this patch tested?
   
   - `robot --dryrun` of the modified test case passes.
   - The `flaky-test-check` workflow only repeats JUnit tests, so it does not 
apply to this acceptance suite. `acceptance (ranger)` in [CI on this 
branch](https://github.com/smengcl/hadoop-ozone/actions/runs/39071485874): in 
progress
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to