[
https://issues.apache.org/jira/browse/RANGER-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran Krishnan resolved RANGER-5640.
-------------------------------------------
Resolution: Fixed
> Align Ranger Ozone Docker with Ozone 2.1 and fix Ozone plugin audit-server /
> getSessionPolicy compatibility
> -----------------------------------------------------------------------------------------------------------
>
> Key: RANGER-5640
> URL: https://issues.apache.org/jira/browse/RANGER-5640
> Project: Ranger
> Issue Type: Task
> Components: Ranger
> Reporter: Ramachandran Krishnan
> Assignee: Ramachandran Krishnan
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ranger’s Ozone plugin compiles against Ozone 2.1.0 ({{{}pom.xml{}}},
> RANGER-5393 / AssumeRole), but {{dev-support/ranger-docker}} still runs Ozone
> 1.4.0 at runtime. That mismatch causes Tier 4 / Docker E2E failures:
> # {{NoSuchMethodError: RequestContext.getSessionPolicy()}} — plugin bytecode
> calls a 2.1 API; Ozone 1.4 OM classpath has no such method → all
> {{checkAccess()}} calls deny.
> # Missing audit-server destination JARs — {{plugin-ozone.xml}} moduleSet
> includes audit modules but binaries whitelist omits {{ranger-audit-core}} /
> {{ranger-audit-dest-auditserver}} → {{providerName=auditserver}} fails at
> runtime.
> Proposed changes:
> * Bump Docker {{OZONE_VERSION}} to 2.1.0 and {{OZONE_RUNNER_VERSION}} to
> 20260106-1-jdk21 (Ozone 2.0+ requires jdk21 runner; multi-arch arm64+amd64).
> * Add explicit audit JAR includes in
> {{{}distro/src/main/assembly/plugin-ozone.xml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
