[jira] [Commented] (RANGER-4076) Support Java 17 for build and runtime
[ https://issues.apache.org/jira/browse/RANGER-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888060#comment-17888060 ] Abhishek Kumar commented on RANGER-4076: [~rakeshgupta264] - CI on GitHub runs all docker containers on a PR, can you please check if the docker-build step passes with your change ? CC: [~madhan] > Support Java 17 for build and runtime > - > > Key: RANGER-4076 > URL: https://issues.apache.org/jira/browse/RANGER-4076 > Project: Ranger > Issue Type: New Feature > Components: admin, build-infra >Reporter: Andrew Luo >Assignee: Rakesh Gupta >Priority: Major > Attachments: > 0001-RANGER-4076-Support-Java-17-for-build-and-runtime.patch > > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4955) Add support to retrieve group information from JWT
Abhishek Kumar created RANGER-4955: -- Summary: Add support to retrieve group information from JWT Key: RANGER-4955 URL: https://issues.apache.org/jira/browse/RANGER-4955 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar ClaimSets are natively supported in JWT, use this to gather group information if present, this is agnostic of the token provider used to retrieve the JWT. for eg: Knox currently provides an option to embed group information when queried with: https://:8443/gateway/homepage/knoxtoken/api/v1/token?knox.token.include.groups=true This would help facilitate checks on groups for the remote user when using JWT auth (for ex: service admin check). It avoids the need to do a UGI lookup for the group based on the remote user. Enable this via a configurable param in ranger-admin-site.xml CC: [~spolavarapu] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4951) CI Build: GitHub Runner is running out of disk space
Abhishek Kumar created RANGER-4951:
--
Summary: CI Build: GitHub Runner is running out of disk space
Key: RANGER-4951
URL: https://issues.apache.org/jira/browse/RANGER-4951
Project: Ranger
Issue Type: Bug
Components: Ranger
Environment: Github Runner: ubuntu-latest
Reporter: Abhishek Kumar
Attachments: Screenshot 2024-10-05 at 10.13.50 PM.png
While running docker-build on master, recent builds are encountering no space
left on device error.
{code:java}
System.IO.IOException: No space left on device :
'/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
TraceEventType eventType, Int32 id)
at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
eventCache, String source, TraceEventType eventType, Int32 id, String message)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32
id, String message)
at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
args)
System.IO.IOException: No space left on device :
'/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
TraceEventType eventType, Int32 id)
at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
eventCache, String source, TraceEventType eventType, Int32 id, String message)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32
id, String message)
at GitHub.Runner.Common.Tracing.Error(Exception exception)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
args)
Unhandled exception. System.IO.IOException: No space left on device :
'/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at System.Diagnostics.TraceSource.Flush()
at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
at GitHub.Runner.Common.TraceManager.Dispose()
at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
at GitHub.Runner.Common.HostContext.Dispose()
at GitHub.Runner.Worker.Program.Main(String[] args) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4951) CI Build: GitHub Runner is running out of disk space
[
https://issues.apache.org/jira/browse/RANGER-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4951:
---
Attachment: Screenshot 2024-10-05 at 10.13.50 PM.png
> CI Build: GitHub Runner is running out of disk space
> -
>
> Key: RANGER-4951
> URL: https://issues.apache.org/jira/browse/RANGER-4951
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Environment: Github Runner: ubuntu-latest
>Reporter: Abhishek Kumar
>Priority: Major
> Attachments: Screenshot 2024-10-05 at 10.13.50 PM.png
>
>
> While running docker-build on master, recent builds are encountering no space
> left on device error.
>
> {code:java}
> System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
> TraceEventType eventType, Int32 id)
>at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
> eventCache, String source, TraceEventType eventType, Int32 id, String message)
>at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType,
> Int32 id, String message)
>at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
>at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
> args)
> System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
> TraceEventType eventType, Int32 id)
>at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
> eventCache, String source, TraceEventType eventType, Int32 id, String message)
>at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType,
> Int32 id, String message)
>at GitHub.Runner.Common.Tracing.Error(Exception exception)
>at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
> args)
> Unhandled exception. System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at System.Diagnostics.TraceSource.Flush()
>at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
>at GitHub.Runner.Common.TraceManager.Dispose()
>at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
>at GitHub.Runner.Common.HostContext.Dispose()
>at GitHub.Runner.Worker.Program.Main(String[] args) {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4929) Fix OzoneManager to run as hadoop
Abhishek Kumar created RANGER-4929: -- Summary: Fix OzoneManager to run as hadoop Key: RANGER-4929 URL: https://issues.apache.org/jira/browse/RANGER-4929 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Abhishek Kumar OzoneManager is a process which runs in the ozone-om container, ranger-ozone plugin gets initialized before the process runs, currently the process runs as root as the installation of ranger-ozone plugin requires root privileges. The OzoneManager process should ideally run as hadoop user, the same user which is used in the ozone runner image. CC: [~smeng] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4929) Fix OzoneManager to run as hadoop in ozone-om container
[ https://issues.apache.org/jira/browse/RANGER-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4929: --- Summary: Fix OzoneManager to run as hadoop in ozone-om container (was: Fix OzoneManager to run as hadoop) > Fix OzoneManager to run as hadoop in ozone-om container > --- > > Key: RANGER-4929 > URL: https://issues.apache.org/jira/browse/RANGER-4929 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Priority: Major > > OzoneManager is a process which runs in the ozone-om container, ranger-ozone > plugin gets initialized before the process runs, currently the process runs > as root as the installation of ranger-ozone plugin requires root privileges. > The OzoneManager process should ideally run as hadoop user, the same user > which is used in the ozone runner image. > CC: [~smeng] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3746) [docker]: Ranger base image on UBI 9 with memory and build optimizations
[ https://issues.apache.org/jira/browse/RANGER-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880801#comment-17880801 ] Abhishek Kumar commented on RANGER-3746: ranger-2.6 commits: - [https://github.com/apache/ranger/commit/8302220] - [https://github.com/apache/ranger/commit/a41162b] > [docker]: Ranger base image on UBI 9 with memory and build optimizations > > > Key: RANGER-3746 > URL: https://issues.apache.org/jira/browse/RANGER-3746 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This aims to to have an additional support for UBI base images for ranger > docker development as an alternative to ubuntu base image currently in place. > Red Hat Universal Base Images (UBI) are OCI-compliant container base > operating system images with complementary runtime languages and packages > that are freely redistributable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3746) [docker]: Ranger base image on UBI 9 with memory and build optimizations
[ https://issues.apache.org/jira/browse/RANGER-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880795#comment-17880795 ] Abhishek Kumar commented on RANGER-3746: Follow-up commit [master]: [https://github.com/apache/ranger/commit/5b22d92] > [docker]: Ranger base image on UBI 9 with memory and build optimizations > > > Key: RANGER-3746 > URL: https://issues.apache.org/jira/browse/RANGER-3746 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This aims to to have an additional support for UBI base images for ranger > docker development as an alternative to ubuntu base image currently in place. > Red Hat Universal Base Images (UBI) are OCI-compliant container base > operating system images with complementary runtime languages and packages > that are freely redistributable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-3746) [docker]: Ranger base image on UBI 9 with memory and build optimizations
[ https://issues.apache.org/jira/browse/RANGER-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-3746. Fix Version/s: 3.0.0 Resolution: Fixed Commit[master]: [https://github.com/apache/ranger/commit/204801c] > [docker]: Ranger base image on UBI 9 with memory and build optimizations > > > Key: RANGER-3746 > URL: https://issues.apache.org/jira/browse/RANGER-3746 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This aims to to have an additional support for UBI base images for ranger > docker development as an alternative to ubuntu base image currently in place. > Red Hat Universal Base Images (UBI) are OCI-compliant container base > operating system images with complementary runtime languages and packages > that are freely redistributable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4925) Cache downloaded archives during CI docker build
[ https://issues.apache.org/jira/browse/RANGER-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4925. Fix Version/s: 3.0.0 Resolution: Fixed Commit [master]: [https://github.com/apache/ranger/commit/705f1bf] > Cache downloaded archives during CI docker build > > > Key: RANGER-4925 > URL: https://issues.apache.org/jira/browse/RANGER-4925 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > > Cache downloaded archives (as part of docker build) in CI runs to optimize > docker build times. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4925) Cache downloaded archives during CI docker build
Abhishek Kumar created RANGER-4925: -- Summary: Cache downloaded archives during CI docker build Key: RANGER-4925 URL: https://issues.apache.org/jira/browse/RANGER-4925 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar Cache downloaded archives (as part of docker build) in CI runs to optimize docker build times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4921) Fix docker compose command in CI
[ https://issues.apache.org/jira/browse/RANGER-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4921. Resolution: Fixed > Fix docker compose command in CI > > > Key: RANGER-4921 > URL: https://issues.apache.org/jira/browse/RANGER-4921 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > docker-compose command changed to docker compose -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4921) Fix docker compose command in CI
[ https://issues.apache.org/jira/browse/RANGER-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877911#comment-17877911 ] Abhishek Kumar commented on RANGER-4921: Commit[master]: [https://github.com/apache/ranger/commit/89879dc] > Fix docker compose command in CI > > > Key: RANGER-4921 > URL: https://issues.apache.org/jira/browse/RANGER-4921 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > docker-compose command changed to docker compose -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4921) Fix docker compose command in CI
[ https://issues.apache.org/jira/browse/RANGER-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4921: --- Summary: Fix docker compose command in CI (was: Update docker compose command in CI) > Fix docker compose command in CI > > > Key: RANGER-4921 > URL: https://issues.apache.org/jira/browse/RANGER-4921 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > docker-compose command changed to docker compose -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4919: --- Affects Version/s: 2.5.0 > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4919: --- Fix Version/s: (was: 2.6.0) > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4919. Resolution: Fixed Commit: [https://github.com/apache/ranger/commit/8bb2053] > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4919: --- Fix Version/s: 2.6.0 > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reassigned RANGER-4919: -- Assignee: Abhishek Kumar > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4921) Update docker compose command in CI
Abhishek Kumar created RANGER-4921: -- Summary: Update docker compose command in CI Key: RANGER-4921 URL: https://issues.apache.org/jira/browse/RANGER-4921 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar docker-compose command changed to docker compose -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3801) Add support for Ozone in docker
[ https://issues.apache.org/jira/browse/RANGER-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876551#comment-17876551 ] Abhishek Kumar commented on RANGER-3801: Hi [~smeng], Here is a PR available, could you take a look: [https://github.com/apache/ranger/pull/377] Thanks! > Add support for Ozone in docker > --- > > Key: RANGER-3801 > URL: https://issues.apache.org/jira/browse/RANGER-3801 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Siyao Meng >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi folks, > I see Ranger has dev support for hadoop, hbase, hive, solr and others. Shall > we add ozone as well? As Ozone does support using > [RangerOzoneAuthorizer|https://github.com/apache/ranger/blob/master/plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java] > as the ACL checker? > https://github.com/apache/ranger/tree/master/dev-support/ranger-docker > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3801) Add support for Ozone in docker
[ https://issues.apache.org/jira/browse/RANGER-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-3801: --- Summary: Add support for Ozone in docker (was: Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml) > Add support for Ozone in docker > --- > > Key: RANGER-3801 > URL: https://issues.apache.org/jira/browse/RANGER-3801 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Siyao Meng >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Hi folks, > I see Ranger has dev support for hadoop, hbase, hive, solr and others. Shall > we add ozone as well? As Ozone does support using > [RangerOzoneAuthorizer|https://github.com/apache/ranger/blob/master/plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java] > as the ACL checker? > https://github.com/apache/ranger/tree/master/dev-support/ranger-docker > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4919: --- Attachment: build.log > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Priority: Major > Attachments: build.log > > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
Abhishek Kumar created RANGER-4919: -- Summary: maven build fails after knox-gateway-version bump to 2.0.0 Key: RANGER-4919 URL: https://issues.apache.org/jira/browse/RANGER-4919 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Abhishek Kumar knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be included in the build: org.jetbrains.pty4j:pty4j:jar:0.11.4, org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 These libraries are not found in apache snapshot mirror, the exact versions are also not present in: - [https://repo.maven.apache.org/] - [https://repo1.maven.org/] Although an upgraded version is available above. [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4918) Add support for Impala-Ranger Integration in docker
Abhishek Kumar created RANGER-4918: -- Summary: Add support for Impala-Ranger Integration in docker Key: RANGER-4918 URL: https://issues.apache.org/jira/browse/RANGER-4918 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar Tracks changes to introduce impala docker image with ranger plugin enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3801) Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml
[ https://issues.apache.org/jira/browse/RANGER-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-3801: --- Issue Type: Improvement (was: Task) > Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml > --- > > Key: RANGER-3801 > URL: https://issues.apache.org/jira/browse/RANGER-3801 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Siyao Meng >Assignee: Abhishek Kumar >Priority: Major > > Hi folks, > I see Ranger has dev support for hadoop, hbase, hive, solr and others. Shall > we add ozone as well? As Ozone does support using > [RangerOzoneAuthorizer|https://github.com/apache/ranger/blob/master/plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java] > as the ACL checker? > https://github.com/apache/ranger/tree/master/dev-support/ranger-docker > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-3801) Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml
[ https://issues.apache.org/jira/browse/RANGER-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reassigned RANGER-3801: -- Assignee: Abhishek Kumar > Add Dockerfile.ranger-ozone and docker-compose.ranger-ozone.yml > --- > > Key: RANGER-3801 > URL: https://issues.apache.org/jira/browse/RANGER-3801 > Project: Ranger > Issue Type: Task > Components: build-infra >Reporter: Siyao Meng >Assignee: Abhishek Kumar >Priority: Major > > Hi folks, > I see Ranger has dev support for hadoop, hbase, hive, solr and others. Shall > we add ozone as well? As Ozone does support using > [RangerOzoneAuthorizer|https://github.com/apache/ranger/blob/master/plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java] > as the ACL checker? > https://github.com/apache/ranger/tree/master/dev-support/ranger-docker > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4907) Optimize user delete operation
[ https://issues.apache.org/jira/browse/RANGER-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874334#comment-17874334 ] Abhishek Kumar commented on RANGER-4907: Hi [~suchnit], Would the approach proposed in RANGER-4246 help in addressing the issue you're observing ? > Optimize user delete operation > -- > > Key: RANGER-4907 > URL: https://issues.apache.org/jira/browse/RANGER-4907 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Subhrat Chaudhary >Assignee: Subhrat Chaudhary >Priority: Major > > If a user has large number of associations with groups, policies, the user > delete operation can take large amount of time, especially while updating the > policies. Since to update a policy, we have large number of validations in > place. This can be even worse, if multiple user delete requests are received > at the same time. We can add following optimizations to improve the user > delete performance: > * Remove foreign key relation of x_user with x_auth_sess, with this we can > skip updating the user references in x_auth_sess when a user is deleted. > * Currently all policy reference for a user are cleaned up and updated ones > are added again. We can remove policy reference only for the user being > deleted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4881) Publish ranger docker images for ranger-2.5 release
[ https://issues.apache.org/jira/browse/RANGER-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4881. Resolution: Fixed > Publish ranger docker images for ranger-2.5 release > --- > > Key: RANGER-4881 > URL: https://issues.apache.org/jira/browse/RANGER-4881 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.5.0 > > > Ranger is available in DockerHub: > [https://hub.docker.com/r/apache/ranger] > release 2.5 should also have ranger image (and its dependencies) published to > DockerHub. > Links to relevant DockerHub registries: > 1. apache/ranger: [https://hub.docker.com/r/apache/ranger] > 2. apache/ranger-db: [https://hub.docker.com/r/apache/ranger-db] > 3. apache/ranger-solr: [https://hub.docker.com/r/apache/ranger-solr] > 4. apache/ranger-zk: [https://hub.docker.com/r/apache/ranger-zk] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4881) Publish ranger docker images for ranger-2.5 release
[ https://issues.apache.org/jira/browse/RANGER-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872527#comment-17872527 ] Abhishek Kumar commented on RANGER-4881: The images have been published to Dockerhub: - [https://hub.docker.com/layers/apache/ranger/2.5.0/images/sha256-7e46c732c2c4bb8b61a740ce2b15e343c0f585e01e56aea3ee48514f889e6f69] - [https://hub.docker.com/layers/apache/ranger-db/2.5.0/images/sha256-f879a28c7bcb7e996c4c693fa959d4655c340feb68a077a6f060544aeaa66bb3?context=explore] - [https://hub.docker.com/layers/apache/ranger-zk/2.5.0/images/sha256-b7229a2703c7fe1b50952e7f439ac10fc8fc3c1f187617bc49799d80b9c18755?context=explore] - [https://hub.docker.com/layers/apache/ranger-solr/2.5.0/images/sha256-89f124b09d4e456c9d7169c328b4408c983bb105bc02cfa1c8d1b09ba296d67b?context=explore] > Publish ranger docker images for ranger-2.5 release > --- > > Key: RANGER-4881 > URL: https://issues.apache.org/jira/browse/RANGER-4881 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.5.0 > > > Ranger is available in DockerHub: > [https://hub.docker.com/r/apache/ranger] > release 2.5 should also have ranger image (and its dependencies) published to > DockerHub. > Links to relevant DockerHub registries: > 1. apache/ranger: [https://hub.docker.com/r/apache/ranger] > 2. apache/ranger-db: [https://hub.docker.com/r/apache/ranger-db] > 3. apache/ranger-solr: [https://hub.docker.com/r/apache/ranger-solr] > 4. apache/ranger-zk: [https://hub.docker.com/r/apache/ranger-zk] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4881) Publish ranger docker images for ranger-2.5 release
[ https://issues.apache.org/jira/browse/RANGER-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reassigned RANGER-4881: -- Assignee: Abhishek Kumar > Publish ranger docker images for ranger-2.5 release > --- > > Key: RANGER-4881 > URL: https://issues.apache.org/jira/browse/RANGER-4881 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.5.0 > > > Ranger is available in DockerHub: > [https://hub.docker.com/r/apache/ranger] > release 2.5 should also have ranger image (and its dependencies) published to > DockerHub. > Links to relevant DockerHub registries: > 1. apache/ranger: [https://hub.docker.com/r/apache/ranger] > 2. apache/ranger-db: [https://hub.docker.com/r/apache/ranger-db] > 3. apache/ranger-solr: [https://hub.docker.com/r/apache/ranger-solr] > 4. apache/ranger-zk: [https://hub.docker.com/r/apache/ranger-zk] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4881) Publish ranger docker images for ranger-2.5 release
[ https://issues.apache.org/jira/browse/RANGER-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4881: --- Description: Ranger is available in DockerHub: [https://hub.docker.com/r/apache/ranger] release 2.5 should also have ranger image (and its dependencies) published to DockerHub. Links to relevant DockerHub registries: 1. apache/ranger: [https://hub.docker.com/r/apache/ranger] 2. apache/ranger-db: [https://hub.docker.com/r/apache/ranger-db] 3. apache/ranger-solr: [https://hub.docker.com/r/apache/ranger-solr] 4. apache/ranger-zk: [https://hub.docker.com/r/apache/ranger-zk] was: Ranger is available in DockerHub: [https://hub.docker.com/r/apache/ranger] release 2.5 should also have ranger image (and its dependencies) published to DockerHub. > Publish ranger docker images for ranger-2.5 release > --- > > Key: RANGER-4881 > URL: https://issues.apache.org/jira/browse/RANGER-4881 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Priority: Major > Fix For: 2.5.0 > > > Ranger is available in DockerHub: > [https://hub.docker.com/r/apache/ranger] > release 2.5 should also have ranger image (and its dependencies) published to > DockerHub. > Links to relevant DockerHub registries: > 1. apache/ranger: [https://hub.docker.com/r/apache/ranger] > 2. apache/ranger-db: [https://hub.docker.com/r/apache/ranger-db] > 3. apache/ranger-solr: [https://hub.docker.com/r/apache/ranger-solr] > 4. apache/ranger-zk: [https://hub.docker.com/r/apache/ranger-zk] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4881) Publish ranger docker images for ranger-2.5 release
Abhishek Kumar created RANGER-4881: -- Summary: Publish ranger docker images for ranger-2.5 release Key: RANGER-4881 URL: https://issues.apache.org/jira/browse/RANGER-4881 Project: Ranger Issue Type: Task Components: Ranger Affects Versions: 2.5.0 Reporter: Abhishek Kumar Fix For: 2.5.0 Ranger is available in DockerHub: [https://hub.docker.com/r/apache/ranger] release 2.5 should also have ranger image (and its dependencies) published to DockerHub. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869540#comment-17869540 ] Abhishek Kumar commented on RANGER-4874: LGTM. Tested ranger and ranger-kms containers: * able to login to ranger UI, services created successfully. * no relevant errors seen ranger.log and catalina.out * all unit tests pass Thank you for the patch. > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 3.0.0, 2.5.0 > > Attachments: RANGER-4874-ranger-2.5.patch, RANGER-4874.patch, > Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot 2024-07-26 at 9.22.44 > PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. > This is observed in docker env for ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869528#comment-17869528 ] Abhishek Kumar commented on RANGER-4874: [~madhan] Thank you for the patch, I'll try it out as well and verify ranger functionality. Thanks! > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 3.0.0, 2.5.0 > > Attachments: RANGER-4874-ranger-2.5.patch, RANGER-4874.patch, > Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot 2024-07-26 at 9.22.44 > PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. > This is observed in docker env for ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4874) Ranger UI inaccessible after login
[
https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869457#comment-17869457
]
Abhishek Kumar edited comment on RANGER-4874 at 7/29/24 9:45 PM:
-
Hi [~madhan],
I'm working on the ranger-2.5 branch, tried bringing up ranger container after
the docker build, the container comes up fine however when I login to the
Ranger UI, I see the same error reported in the logs attached. When looking for
the Response class occurrences, this time however the 3rd jar (
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jsr311-api-1.1.1.jar
)was not found since it was built including this
[change|https://github.com/apache/ranger/commit/6025a29].
{code:java}
ranger@ranger:/var/log/ranger$ find /opt/ranger/admin/ -name "*.jar" -exec
fgrep -l javax/ws/rs/core/Response {} \;
/opt/ranger/admin/ews/webapp/WEB-INF/lib/javax.ws.rs-api-2.1.1.jar
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jersey-bundle-1.19.3.jar
ranger@ranger:/var/log/ranger$ {code}
Thanks!
was (Author: abhi_2110):
Hi [~madhan],
I'm working on the ranger-2.5 branch, tried bringing up ranger container after
the docker build, the container comes up fine however when I login to the
Ranger UI, I see the same error reported in the logs attached. When looking for
the Response class occurrences, this time however the 3rd jar was not found
since it was built including this
[change|https://github.com/apache/ranger/commit/6025a29].
{code:java}
ranger@ranger:/var/log/ranger$ find /opt/ranger/admin/ -name "*.jar" -exec
fgrep -l javax/ws/rs/core/Response {} \;
/opt/ranger/admin/ews/webapp/WEB-INF/lib/javax.ws.rs-api-2.1.1.jar
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jersey-bundle-1.19.3.jar
ranger@ranger:/var/log/ranger$ {code}
Thanks!
> Ranger UI inaccessible after login
> ---
>
> Key: RANGER-4874
> URL: https://issues.apache.org/jira/browse/RANGER-4874
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: RANGER-4874-ranger-2.5.patch, RANGER-4874.patch,
> Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot 2024-07-26 at 9.22.44
> PM.png, catalina_error.out, ranger_error.log
>
>
> Ranger UI is not accessible after login although login is successful. Errors
> seen in catalina.out and ranger.log.
> This is observed in docker env for ranger.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4874) Ranger UI inaccessible after login
[
https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869457#comment-17869457
]
Abhishek Kumar edited comment on RANGER-4874 at 7/29/24 9:45 PM:
-
Hi [~madhan],
I'm working on the ranger-2.5 branch, tried bringing up ranger container after
the docker build, the container comes up fine however when I login to the
Ranger UI, I see the same error reported in the logs attached. When looking for
the Response class occurrences, this time however the 3rd jar
(/opt/ranger/admin/ews/webapp/WEB-INF/lib/jsr311-api-1.1.1.jar) was not found
since it was built including this
[change|https://github.com/apache/ranger/commit/6025a29].
{code:java}
ranger@ranger:/var/log/ranger$ find /opt/ranger/admin/ -name "*.jar" -exec
fgrep -l javax/ws/rs/core/Response {} \;
/opt/ranger/admin/ews/webapp/WEB-INF/lib/javax.ws.rs-api-2.1.1.jar
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jersey-bundle-1.19.3.jar
ranger@ranger:/var/log/ranger$ {code}
Thanks!
was (Author: abhi_2110):
Hi [~madhan],
I'm working on the ranger-2.5 branch, tried bringing up ranger container after
the docker build, the container comes up fine however when I login to the
Ranger UI, I see the same error reported in the logs attached. When looking for
the Response class occurrences, this time however the 3rd jar (
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jsr311-api-1.1.1.jar
)was not found since it was built including this
[change|https://github.com/apache/ranger/commit/6025a29].
{code:java}
ranger@ranger:/var/log/ranger$ find /opt/ranger/admin/ -name "*.jar" -exec
fgrep -l javax/ws/rs/core/Response {} \;
/opt/ranger/admin/ews/webapp/WEB-INF/lib/javax.ws.rs-api-2.1.1.jar
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jersey-bundle-1.19.3.jar
ranger@ranger:/var/log/ranger$ {code}
Thanks!
> Ranger UI inaccessible after login
> ---
>
> Key: RANGER-4874
> URL: https://issues.apache.org/jira/browse/RANGER-4874
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: RANGER-4874-ranger-2.5.patch, RANGER-4874.patch,
> Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot 2024-07-26 at 9.22.44
> PM.png, catalina_error.out, ranger_error.log
>
>
> Ranger UI is not accessible after login although login is successful. Errors
> seen in catalina.out and ranger.log.
> This is observed in docker env for ranger.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4874) Ranger UI inaccessible after login
[
https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869457#comment-17869457
]
Abhishek Kumar commented on RANGER-4874:
Hi [~madhan],
I'm working on the ranger-2.5 branch, tried bringing up ranger container after
the docker build, the container comes up fine however when I login to the
Ranger UI, I see the same error reported in the logs attached. When looking for
the Response class occurrences, this time however the 3rd jar was not found
since it was built including this
[change|https://github.com/apache/ranger/commit/6025a29].
{code:java}
ranger@ranger:/var/log/ranger$ find /opt/ranger/admin/ -name "*.jar" -exec
fgrep -l javax/ws/rs/core/Response {} \;
/opt/ranger/admin/ews/webapp/WEB-INF/lib/javax.ws.rs-api-2.1.1.jar
/opt/ranger/admin/ews/webapp/WEB-INF/lib/jersey-bundle-1.19.3.jar
ranger@ranger:/var/log/ranger$ {code}
Thanks!
> Ranger UI inaccessible after login
> ---
>
> Key: RANGER-4874
> URL: https://issues.apache.org/jira/browse/RANGER-4874
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: RANGER-4874-ranger-2.5.patch, RANGER-4874.patch,
> Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot 2024-07-26 at 9.22.44
> PM.png, catalina_error.out, ranger_error.log
>
>
> Ranger UI is not accessible after login although login is successful. Errors
> seen in catalina.out and ranger.log.
> This is observed in docker env for ranger.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4873) update zookeeper version from 3.5.5 to 3.9.2
[ https://issues.apache.org/jira/browse/RANGER-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869456#comment-17869456 ] Abhishek Kumar commented on RANGER-4873: Additional commit details: master: [https://github.com/apache/ranger/commit/9ea9db6] ranger-2.5: [https://github.com/apache/ranger/commit/d5605b3] > update zookeeper version from 3.5.5 to 3.9.2 > > > Key: RANGER-4873 > URL: https://issues.apache.org/jira/browse/RANGER-4873 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Krzysztof Sobolewski >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > This Jira tracks [pull request > #359|https://github.com/apache/ranger/pull/359]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4874: --- Description: Ranger UI is not accessible after login although login is successful. Errors seen in catalina.out and ranger.log. This is observed in docker env for ranger. was: Ranger UI is not accessible after login although login is successful. Errors seen in catalina.out and ranger.log. > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Priority: Critical > Attachments: Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot > 2024-07-26 at 9.22.44 PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. > This is observed in docker env for ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4874: --- Attachment: ranger_error.log > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Priority: Critical > Attachments: Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot > 2024-07-26 at 9.22.44 PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4874) Ranger UI inaccessible after login
Abhishek Kumar created RANGER-4874: -- Summary: Ranger UI inaccessible after login Key: RANGER-4874 URL: https://issues.apache.org/jira/browse/RANGER-4874 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.5.0 Reporter: Abhishek Kumar Attachments: Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot 2024-07-26 at 9.22.44 PM.png, catalina_error.out, ranger_error.log Ranger UI is not accessible after login although login is successful. Errors seen in catalina.out and ranger.log. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4874: --- Attachment: catalina_error.out > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Priority: Critical > Attachments: Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot > 2024-07-26 at 9.22.44 PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4874: --- Attachment: Screenshot 2024-07-26 at 9.22.44 PM.png > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Priority: Critical > Attachments: Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot > 2024-07-26 at 9.22.44 PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4874) Ranger UI inaccessible after login
[ https://issues.apache.org/jira/browse/RANGER-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4874: --- Attachment: Screenshot 2024-07-26 at 7.52.48 PM.png > Ranger UI inaccessible after login > --- > > Key: RANGER-4874 > URL: https://issues.apache.org/jira/browse/RANGER-4874 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Priority: Critical > Attachments: Screenshot 2024-07-26 at 7.52.48 PM.png, Screenshot > 2024-07-26 at 9.22.44 PM.png, catalina_error.out, ranger_error.log > > > Ranger UI is not accessible after login although login is successful. Errors > seen in catalina.out and ranger.log. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-2846. Resolution: Fixed > Add support for resource[volume, bucket, key] look up in ozone plugin > - > > Key: RANGER-2846 > URL: https://issues.apache.org/jira/browse/RANGER-2846 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.1.0 >Reporter: Abhishek Shukla >Assignee: Abhishek Kumar >Priority: Blocker > Labels: ozone > Fix For: 2.5.0 > > > The task to add support for resource [volume, bucket, key] lookup while > creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867157#comment-17867157 ] Abhishek Kumar commented on RANGER-2846: Present in ranger-2.5: https://github.com/apache/ranger/commit/3c68de38b6c40ffa8f015a1e01d4928209cbf7d3 > Add support for resource[volume, bucket, key] look up in ozone plugin > - > > Key: RANGER-2846 > URL: https://issues.apache.org/jira/browse/RANGER-2846 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.1.0 >Reporter: Abhishek Shukla >Assignee: Abhishek Kumar >Priority: Blocker > Labels: ozone > Fix For: 2.5.0 > > > The task to add support for resource [volume, bucket, key] lookup while > creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4074) assignPermissionToUser in XUserMgr creates entries with NULL moduleId in x_user_module_perm
[ https://issues.apache.org/jira/browse/RANGER-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4074. Resolution: Fixed Merged in ranger-2.5: https://github.com/apache/ranger/commit/7542bbdcf2f6f07c346fb58ebfc86350f79753e1 > assignPermissionToUser in XUserMgr creates entries with NULL moduleId in > x_user_module_perm > --- > > Key: RANGER-4074 > URL: https://issues.apache.org/jira/browse/RANGER-4074 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.2.0, 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > assignPermissionToUser method assigns permissions for a module (which does > not exist) to users with Auditor role. > h1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4849) [dependabot] update Python library versions referenced in ranger-tools module
[ https://issues.apache.org/jira/browse/RANGER-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867154#comment-17867154 ] Abhishek Kumar commented on RANGER-4849: Merged additional changes to master and ranger-2.5: https://github.com/apache/ranger/commit/967e2a53d983176336f69ec09718be501e984b7e https://github.com/apache/ranger/commit/7c5a27ae08715b9ac3a06e23371a05f527ae86b1 > [dependabot] update Python library versions referenced in ranger-tools module > - > > Key: RANGER-4849 > URL: https://issues.apache.org/jira/browse/RANGER-4849 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Attachments: RANGER-4849.patch > > Time Spent: 20m > Remaining Estimate: 0h > > This Jira tracks merge of dependent library version updates suggested in > following pull requests: > * [https://github.com/apache/ranger/pull/182] (Pillows) > * [https://github.com/apache/ranger/pull/260] (requests) > * [https://github.com/apache/ranger/pull/270] (scipy) > * [https://github.com/apache/ranger/pull/275] (certifi) > * [https://github.com/apache/ranger/pull/323] (idna) > * [https://github.com/apache/ranger/pull/324] (jinja2) > * [https://github.com/apache/ranger/pull/325] (urllib3) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-2847) Add support/Fix Test connection with Ozone service
[
https://issues.apache.org/jira/browse/RANGER-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-2847.
Resolution: Fixed
Present in ranger-2.5:
https://github.com/apache/ranger/commit/3c68de38b6c40ffa8f015a1e01d4928209cbf7d3
> Add support/Fix Test connection with Ozone service
> --
>
> Key: RANGER-2847
> URL: https://issues.apache.org/jira/browse/RANGER-2847
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: Abhishek Shukla
>Assignee: Abhishek Kumar
>Priority: Blocker
> Labels: ozone
> Fix For: 2.5.0
>
>
> Currently, Test Connection with Ozone Service is failing with this error.
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/ozone/client/OzoneClientFactory.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-4071) Support for LDAP/AD usernames and group names with special chars
[
https://issues.apache.org/jira/browse/RANGER-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-4071.
Resolution: Fixed
> Support for LDAP/AD usernames and group names with special chars
>
>
> Key: RANGER-4071
> URL: https://issues.apache.org/jira/browse/RANGER-4071
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
>Affects Versions: 2.3.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ranger usersync regards the forward slash ('/') as a separator character in
> the regex so it ignores it if you actually want to use it in your groupname.
> e.g. RRR/group_name_suffix
> Using a different character like + in the regex works to get something like
> RRR+group_name_suffix but not RRR/group_name_suffix. / can be used as a
> domain separator in AD groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4071) Support for LDAP/AD usernames and group names with special chars
[
https://issues.apache.org/jira/browse/RANGER-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867150#comment-17867150
]
Abhishek Kumar commented on RANGER-4071:
Present in ranger-2.5:
https://github.com/apache/ranger/commit/c1f34c4ce6372f42da17387eb80f473b75d95dd7
> Support for LDAP/AD usernames and group names with special chars
>
>
> Key: RANGER-4071
> URL: https://issues.apache.org/jira/browse/RANGER-4071
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
>Affects Versions: 2.3.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ranger usersync regards the forward slash ('/') as a separator character in
> the regex so it ignores it if you actually want to use it in your groupname.
> e.g. RRR/group_name_suffix
> Using a different character like + in the regex works to get something like
> RRR+group_name_suffix but not RRR/group_name_suffix. / can be used as a
> domain separator in AD groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-4064) RANGER-3348 introduces bug in python client for SSL enabled clusters
[
https://issues.apache.org/jira/browse/RANGER-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-4064.
Resolution: Fixed
Present in ranger-2.4:
https://github.com/apache/ranger/commit/e5389eba12fe9c1bd71a8a29e49c6297e4a06dc0
> RANGER-3348 introduces bug in python client for SSL enabled clusters
>
>
> Key: RANGER-4064
> URL: https://issues.apache.org/jira/browse/RANGER-4064
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Blocker
> Fix For: 3.0.0, 2.4.0
>
>
> Bug was introduced in RANGER-3348 wherein using the python client on an SSL
> enabled cluster w/o host verification is no longer possible.
> ranger.session.verify = False # this was used to skip host verification
> earlier whereas in current code it is not possible to do so.
> >>> from apache_ranger.model.ranger_service import *
> >>> from apache_ranger.client.ranger_client import *
> >>> from apache_ranger.model.ranger_policy import *
> >>> ranger_url = 'someurl'
> >>> ranger_auth = ('admin', 'X')
> >>> from requests_kerberos import HTTPKerberosAuth
> >>> ranger_auth = HTTPKerberosAuth()
> >>> ranger = RangerClient(ranger_url, ranger_auth)
> >>> ranger.
> Display all 123 possibilities? (y or n)
> >>> ranger.session.verify = True
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'RangerClient' object has no attribute 'session'
> CC: [~kishor.gollapalliwar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4064) RANGER-3348 introduces bug in python client for SSL enabled clusters
[
https://issues.apache.org/jira/browse/RANGER-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4064:
---
Fix Version/s: 2.4.0
(was: 2.5.0)
> RANGER-3348 introduces bug in python client for SSL enabled clusters
>
>
> Key: RANGER-4064
> URL: https://issues.apache.org/jira/browse/RANGER-4064
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Blocker
> Fix For: 3.0.0, 2.4.0
>
>
> Bug was introduced in RANGER-3348 wherein using the python client on an SSL
> enabled cluster w/o host verification is no longer possible.
> ranger.session.verify = False # this was used to skip host verification
> earlier whereas in current code it is not possible to do so.
> >>> from apache_ranger.model.ranger_service import *
> >>> from apache_ranger.client.ranger_client import *
> >>> from apache_ranger.model.ranger_policy import *
> >>> ranger_url = 'someurl'
> >>> ranger_auth = ('admin', 'X')
> >>> from requests_kerberos import HTTPKerberosAuth
> >>> ranger_auth = HTTPKerberosAuth()
> >>> ranger = RangerClient(ranger_url, ranger_auth)
> >>> ranger.
> Display all 123 possibilities? (y or n)
> >>> ranger.session.verify = True
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'RangerClient' object has no attribute 'session'
> CC: [~kishor.gollapalliwar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4116) Define description/topics/merge strategy for the github repository with .asf.yaml
[ https://issues.apache.org/jira/browse/RANGER-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867120#comment-17867120 ] Abhishek Kumar commented on RANGER-4116: Merged to ranger-2.5: https://github.com/apache/ranger/commit/ed2fa3687e9eccad666eec2403a7331406d32b24 https://github.com/apache/ranger/commit/6461b2615e201ee1091830150c06434fb97794e3 > Define description/topics/merge strategy for the github repository with > .asf.yaml > - > > Key: RANGER-4116 > URL: https://issues.apache.org/jira/browse/RANGER-4116 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > .asf.yaml helps to set different parameters on github repositories without > admin privileges: > [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features] > This basic .asf.yaml defines description/url/topics and the allowed merge > buttons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4829) Atlas policy engine tests need fix
[
https://issues.apache.org/jira/browse/RANGER-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867116#comment-17867116
]
Abhishek Kumar commented on RANGER-4829:
Merged to master:
https://github.com/apache/ranger/commit/f806430350d06652572a791e7218dc100fa63751,
you may close the jira.
> Atlas policy engine tests need fix
> --
>
> Key: RANGER-4829
> URL: https://issues.apache.org/jira/browse/RANGER-4829
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Fateh Singh
>Assignee: Fateh Singh
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> # Tthe "level" for entity be 3 here and not 2
> {code:java}
> "resources":[
> {"name":"entity-type","level":1,"mandatory":true,"lookupSupported":true,"matcher":"org.apache.ranger.plugin.resourcematcher.RangerDefaultResourceMatcher","matcherOptions":{"wildCard":true,
> "ignoreCase":true},"label":"Entity Type","description":"Entity Type"},
> {"name":"entity-classification","level":2,"parent":"entity-type","mandatory":true,"lookupSupported":true,"matcher":"org.apache.ranger.plugin.resourcematcher.RangerDefaultResourceMatcher","matcherOptions":{"wildCard":true,
> "ignoreCase":true},"label":"Entity Classification","description":"Entity
> Classification"},
> {"name":"entity","level":2,"parent":"entity-classification","mandatory":true,"lookupSupported":true,"matcher":"org.apache.ranger.plugin.resourcematcher.RangerDefaultResourceMatcher","matcherOptions":{"wildCard":true,
> "ignoreCase":true},"label":"Entity ID","description":"Entity ID"} ],{code}
>
> 2. For any of the test cases, the resource looks like this
> {code:java}
> "resource":{"elements":{"entity-type":"DataSet", "entity-classification":[]},
> "entity":"default@cl1"},{code}
> When policy engine creates test case for this, there are just 2 elements in
> the resource (entity-type and classification) -- "entity" is totally skipped
> in the resource..
> According to me, it should look like
> {code:java}
> "resource":{"elements":{"entity-type":"DataSet", "entity-classification":[],
> "entity":"default@cl1"}}{code}
> This results in resource having 3 elements which I would expect.
> If there are just 2 elements then resource matching ignores the "entity"
> completely during evaluation which results in incorrect access denied for the
> below test scenario
> {code:java}
> "policies":[ { "id":30,"name":"policy for allow
> test_atlas","isEnabled":true,"isAuditEnabled":true,
> "resources":{"entity-type":{"values":["abc"]},"entity-classification":{"values":["PII"]},"entity":{"values":["test_atlas"]}},
> "policyItems":[ {"accesses":[{"type":"entity-read",
> "isAllowed":true}],"users":["user1"],"groups":["g1"],"delegateAdmin":false} ]
> } ], "tests":[ {"name":"DataSet read by a data-steward", "request":{
> "resource":{"elements":{"entity-type":["abc"],
> "entity-classification":["PII"]}, "entity":"test_atlas"},
> "accessType":"entity-read","user":"user1","userGroups":["g1"] },
> "result":{"isAudited":true,"isAllowed":true,"policyId":30} }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-2847) Add support/Fix Test connection with Ozone service
[
https://issues.apache.org/jira/browse/RANGER-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-2847:
---
Priority: Blocker (was: Major)
> Add support/Fix Test connection with Ozone service
> --
>
> Key: RANGER-2847
> URL: https://issues.apache.org/jira/browse/RANGER-2847
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: Abhishek Shukla
>Assignee: Abhishek Kumar
>Priority: Blocker
> Labels: ozone
> Fix For: 2.5.0
>
>
> Currently, Test Connection with Ozone Service is failing with this error.
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/ozone/client/OzoneClientFactory.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (RANGER-2847) Add support/Fix Test connection with Ozone service
[
https://issues.apache.org/jira/browse/RANGER-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar reopened RANGER-2847:
> Add support/Fix Test connection with Ozone service
> --
>
> Key: RANGER-2847
> URL: https://issues.apache.org/jira/browse/RANGER-2847
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: Abhishek Shukla
>Assignee: Abhishek Kumar
>Priority: Major
> Labels: ozone
> Fix For: 2.5.0
>
>
> Currently, Test Connection with Ozone Service is failing with this error.
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/ozone/client/OzoneClientFactory.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-2846: --- Fix Version/s: 2.5.0 (was: 2.3.0) > Add support for resource[volume, bucket, key] look up in ozone plugin > - > > Key: RANGER-2846 > URL: https://issues.apache.org/jira/browse/RANGER-2846 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.1.0 >Reporter: Abhishek Shukla >Assignee: Abhishek Kumar >Priority: Major > Labels: ozone > Fix For: 2.5.0 > > > The task to add support for resource [volume, bucket, key] lookup while > creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-2847) Add support/Fix Test connection with Ozone service
[
https://issues.apache.org/jira/browse/RANGER-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-2847:
---
Fix Version/s: 2.5.0
(was: 2.3.0)
> Add support/Fix Test connection with Ozone service
> --
>
> Key: RANGER-2847
> URL: https://issues.apache.org/jira/browse/RANGER-2847
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: Abhishek Shukla
>Assignee: Abhishek Kumar
>Priority: Major
> Labels: ozone
> Fix For: 2.5.0
>
>
> Currently, Test Connection with Ozone Service is failing with this error.
> {noformat}
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/ozone/client/OzoneClientFactory.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-2846: --- Priority: Blocker (was: Major) > Add support for resource[volume, bucket, key] look up in ozone plugin > - > > Key: RANGER-2846 > URL: https://issues.apache.org/jira/browse/RANGER-2846 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.1.0 >Reporter: Abhishek Shukla >Assignee: Abhishek Kumar >Priority: Blocker > Labels: ozone > Fix For: 2.5.0 > > > The task to add support for resource [volume, bucket, key] lookup while > creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (RANGER-2846) Add support for resource[volume, bucket, key] look up in ozone plugin
[ https://issues.apache.org/jira/browse/RANGER-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reopened RANGER-2846: > Add support for resource[volume, bucket, key] look up in ozone plugin > - > > Key: RANGER-2846 > URL: https://issues.apache.org/jira/browse/RANGER-2846 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.1.0 >Reporter: Abhishek Shukla >Assignee: Abhishek Kumar >Priority: Major > Labels: ozone > Fix For: 2.5.0 > > > The task to add support for resource [volume, bucket, key] lookup while > creating ozone policy in ranger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4071) Support for LDAP/AD usernames and group names with special chars
[
https://issues.apache.org/jira/browse/RANGER-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4071:
---
Fix Version/s: 2.5.0
(was: 2.4.0)
> Support for LDAP/AD usernames and group names with special chars
>
>
> Key: RANGER-4071
> URL: https://issues.apache.org/jira/browse/RANGER-4071
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
>Affects Versions: 2.3.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ranger usersync regards the forward slash ('/') as a separator character in
> the regex so it ignores it if you actually want to use it in your groupname.
> e.g. RRR/group_name_suffix
> Using a different character like + in the regex works to get something like
> RRR+group_name_suffix but not RRR/group_name_suffix. / can be used as a
> domain separator in AD groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4071) Support for LDAP/AD usernames and group names with special chars
[
https://issues.apache.org/jira/browse/RANGER-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4071:
---
Priority: Blocker (was: Major)
> Support for LDAP/AD usernames and group names with special chars
>
>
> Key: RANGER-4071
> URL: https://issues.apache.org/jira/browse/RANGER-4071
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
>Affects Versions: 2.3.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ranger usersync regards the forward slash ('/') as a separator character in
> the regex so it ignores it if you actually want to use it in your groupname.
> e.g. RRR/group_name_suffix
> Using a different character like + in the regex works to get something like
> RRR+group_name_suffix but not RRR/group_name_suffix. / can be used as a
> domain separator in AD groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (RANGER-4071) Support for LDAP/AD usernames and group names with special chars
[
https://issues.apache.org/jira/browse/RANGER-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar reopened RANGER-4071:
> Support for LDAP/AD usernames and group names with special chars
>
>
> Key: RANGER-4071
> URL: https://issues.apache.org/jira/browse/RANGER-4071
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
>Affects Versions: 2.3.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ranger usersync regards the forward slash ('/') as a separator character in
> the regex so it ignores it if you actually want to use it in your groupname.
> e.g. RRR/group_name_suffix
> Using a different character like + in the regex works to get something like
> RRR+group_name_suffix but not RRR/group_name_suffix. / can be used as a
> domain separator in AD groups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (RANGER-4074) assignPermissionToUser in XUserMgr creates entries with NULL moduleId in x_user_module_perm
[ https://issues.apache.org/jira/browse/RANGER-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reopened RANGER-4074: > assignPermissionToUser in XUserMgr creates entries with NULL moduleId in > x_user_module_perm > --- > > Key: RANGER-4074 > URL: https://issues.apache.org/jira/browse/RANGER-4074 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.2.0, 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > assignPermissionToUser method assigns permissions for a module (which does > not exist) to users with Auditor role. > h1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4074) assignPermissionToUser in XUserMgr creates entries with NULL moduleId in x_user_module_perm
[ https://issues.apache.org/jira/browse/RANGER-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4074: --- Priority: Blocker (was: Major) > assignPermissionToUser in XUserMgr creates entries with NULL moduleId in > x_user_module_perm > --- > > Key: RANGER-4074 > URL: https://issues.apache.org/jira/browse/RANGER-4074 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.2.0, 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > assignPermissionToUser method assigns permissions for a module (which does > not exist) to users with Auditor role. > h1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4074) assignPermissionToUser in XUserMgr creates entries with NULL moduleId in x_user_module_perm
[ https://issues.apache.org/jira/browse/RANGER-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4074: --- Fix Version/s: 2.5.0 (was: 2.4.0) > assignPermissionToUser in XUserMgr creates entries with NULL moduleId in > x_user_module_perm > --- > > Key: RANGER-4074 > URL: https://issues.apache.org/jira/browse/RANGER-4074 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 2.2.0, 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > assignPermissionToUser method assigns permissions for a module (which does > not exist) to users with Auditor role. > h1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4116) Define description/topics/merge strategy for the github repository with .asf.yaml
[ https://issues.apache.org/jira/browse/RANGER-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4116: --- Fix Version/s: 2.5.0 (was: 2.4.0) > Define description/topics/merge strategy for the github repository with > .asf.yaml > - > > Key: RANGER-4116 > URL: https://issues.apache.org/jira/browse/RANGER-4116 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.3.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > .asf.yaml helps to set different parameters on github repositories without > admin privileges: > [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features] > This basic .asf.yaml defines description/url/topics and the allowed merge > buttons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4064) RANGER-3348 introduces bug in python client for SSL enabled clusters
[
https://issues.apache.org/jira/browse/RANGER-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4064:
---
Priority: Blocker (was: Major)
> RANGER-3348 introduces bug in python client for SSL enabled clusters
>
>
> Key: RANGER-4064
> URL: https://issues.apache.org/jira/browse/RANGER-4064
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
>
> Bug was introduced in RANGER-3348 wherein using the python client on an SSL
> enabled cluster w/o host verification is no longer possible.
> ranger.session.verify = False # this was used to skip host verification
> earlier whereas in current code it is not possible to do so.
> >>> from apache_ranger.model.ranger_service import *
> >>> from apache_ranger.client.ranger_client import *
> >>> from apache_ranger.model.ranger_policy import *
> >>> ranger_url = 'someurl'
> >>> ranger_auth = ('admin', 'X')
> >>> from requests_kerberos import HTTPKerberosAuth
> >>> ranger_auth = HTTPKerberosAuth()
> >>> ranger = RangerClient(ranger_url, ranger_auth)
> >>> ranger.
> Display all 123 possibilities? (y or n)
> >>> ranger.session.verify = True
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'RangerClient' object has no attribute 'session'
> CC: [~kishor.gollapalliwar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4064) RANGER-3348 introduces bug in python client for SSL enabled clusters
[
https://issues.apache.org/jira/browse/RANGER-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4064:
---
Fix Version/s: 2.5.0
> RANGER-3348 introduces bug in python client for SSL enabled clusters
>
>
> Key: RANGER-4064
> URL: https://issues.apache.org/jira/browse/RANGER-4064
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 3.0.0, 2.5.0
>
>
> Bug was introduced in RANGER-3348 wherein using the python client on an SSL
> enabled cluster w/o host verification is no longer possible.
> ranger.session.verify = False # this was used to skip host verification
> earlier whereas in current code it is not possible to do so.
> >>> from apache_ranger.model.ranger_service import *
> >>> from apache_ranger.client.ranger_client import *
> >>> from apache_ranger.model.ranger_policy import *
> >>> ranger_url = 'someurl'
> >>> ranger_auth = ('admin', 'X')
> >>> from requests_kerberos import HTTPKerberosAuth
> >>> ranger_auth = HTTPKerberosAuth()
> >>> ranger = RangerClient(ranger_url, ranger_auth)
> >>> ranger.
> Display all 123 possibilities? (y or n)
> >>> ranger.session.verify = True
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'RangerClient' object has no attribute 'session'
> CC: [~kishor.gollapalliwar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (RANGER-4064) RANGER-3348 introduces bug in python client for SSL enabled clusters
[
https://issues.apache.org/jira/browse/RANGER-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar reopened RANGER-4064:
> RANGER-3348 introduces bug in python client for SSL enabled clusters
>
>
> Key: RANGER-4064
> URL: https://issues.apache.org/jira/browse/RANGER-4064
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 3.0.0
>
>
> Bug was introduced in RANGER-3348 wherein using the python client on an SSL
> enabled cluster w/o host verification is no longer possible.
> ranger.session.verify = False # this was used to skip host verification
> earlier whereas in current code it is not possible to do so.
> >>> from apache_ranger.model.ranger_service import *
> >>> from apache_ranger.client.ranger_client import *
> >>> from apache_ranger.model.ranger_policy import *
> >>> ranger_url = 'someurl'
> >>> ranger_auth = ('admin', 'X')
> >>> from requests_kerberos import HTTPKerberosAuth
> >>> ranger_auth = HTTPKerberosAuth()
> >>> ranger = RangerClient(ranger_url, ranger_auth)
> >>> ranger.
> Display all 123 possibilities? (y or n)
> >>> ranger.session.verify = True
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'RangerClient' object has no attribute 'session'
> CC: [~kishor.gollapalliwar]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4743) [JDK 11]: Fix ranger admin logging
[ https://issues.apache.org/jira/browse/RANGER-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4743: --- Priority: Blocker (was: Major) > [JDK 11]: Fix ranger admin logging > --- > > Key: RANGER-4743 > URL: https://issues.apache.org/jira/browse/RANGER-4743 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Blocker > Fix For: 2.5.0 > > Attachments: 0001-RANGER-4743.patch > > > Currently, the ranger-admin logs do not appear when built and run with jdk 11. > Logback and slf4j versions need to be upgraded to fix the above issue. > More info: [https://logback.qos.ch/download.html] > CC: [~rmani] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4743) [JDK 11]: Fix ranger admin logging
[ https://issues.apache.org/jira/browse/RANGER-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4743: --- Fix Version/s: 2.5.0 > [JDK 11]: Fix ranger admin logging > --- > > Key: RANGER-4743 > URL: https://issues.apache.org/jira/browse/RANGER-4743 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.5.0 > > Attachments: 0001-RANGER-4743.patch > > > Currently, the ranger-admin logs do not appear when built and run with jdk 11. > Logback and slf4j versions need to be upgraded to fix the above issue. > More info: [https://logback.qos.ch/download.html] > CC: [~rmani] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4861) CI: Run and monitor docker containers
Abhishek Kumar created RANGER-4861: -- Summary: CI: Run and monitor docker containers Key: RANGER-4861 URL: https://issues.apache.org/jira/browse/RANGER-4861 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar Once docker builds are enabled, this jira tracks the changes to bring up docker containers for all images built and check if the containers come up fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4837) Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
[
https://issues.apache.org/jira/browse/RANGER-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4837:
---
Fix Version/s: 3.0.0
2.5.0
> Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
>
>
> Key: RANGER-4837
> URL: https://issues.apache.org/jira/browse/RANGER-4837
> Project: Ranger
> Issue Type: Bug
> Components: audit
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Fateh Singh
>Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Below is the intermittent test failure observed:
> {code:java}
> 2024-06-29T00:04:41.5790918Z Tests run: 12, Failures: 1, Errors: 0, Skipped:
> 0, Time elapsed: 627.963 sec <<< FAILURE! - in
> org.apache.ranger.audit.TestAuditQueue
> 2024-06-29T00:04:41.5800847Z
> testAuditFileQueueSpoolORCRollover(org.apache.ranger.audit.TestAuditQueue)
> Time elapsed: 549.462 sec <<< FAILURE!
> 2024-06-29T00:04:41.5802113Z java.lang.AssertionError: File created
> 2024-06-29T00:04:41.5870847Z at org.junit.Assert.fail(Assert.java:89)
> 2024-06-29T00:04:41.5871624Z at org.junit.Assert.assertTrue(Assert.java:42)
> 2024-06-29T00:04:41.5875524Z at
> org.apache.ranger.audit.TestAuditQueue.testAuditFileQueueSpoolORCRollover(TestAuditQueue.java:804)
> {code}
> Run1: [failure]:
> [https://github.com/apache/ranger/actions/runs/9719764431/job/26830107611?pr=321]
> Run2: [pass]:
> [https://github.com/apache/ranger/actions/runs/9719764431/job/26831441560]
> CC: [~rmani]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4837) Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
[
https://issues.apache.org/jira/browse/RANGER-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866169#comment-17866169
]
Abhishek Kumar commented on RANGER-4837:
Thanks for the patch, merged the changes in master and ranger-2.5 branches:
[https://github.com/apache/ranger/commit/c9361dc1c4b02c5271db28c59893a574983353ed]
[https://github.com/apache/ranger/commit/8a6c423d66fd8fc6dbdd60c1ed1fc17438f9e134]
You may close the jira.
> Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
>
>
> Key: RANGER-4837
> URL: https://issues.apache.org/jira/browse/RANGER-4837
> Project: Ranger
> Issue Type: Bug
> Components: audit
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Fateh Singh
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Below is the intermittent test failure observed:
> {code:java}
> 2024-06-29T00:04:41.5790918Z Tests run: 12, Failures: 1, Errors: 0, Skipped:
> 0, Time elapsed: 627.963 sec <<< FAILURE! - in
> org.apache.ranger.audit.TestAuditQueue
> 2024-06-29T00:04:41.5800847Z
> testAuditFileQueueSpoolORCRollover(org.apache.ranger.audit.TestAuditQueue)
> Time elapsed: 549.462 sec <<< FAILURE!
> 2024-06-29T00:04:41.5802113Z java.lang.AssertionError: File created
> 2024-06-29T00:04:41.5870847Z at org.junit.Assert.fail(Assert.java:89)
> 2024-06-29T00:04:41.5871624Z at org.junit.Assert.assertTrue(Assert.java:42)
> 2024-06-29T00:04:41.5875524Z at
> org.apache.ranger.audit.TestAuditQueue.testAuditFileQueueSpoolORCRollover(TestAuditQueue.java:804)
> {code}
> Run1: [failure]:
> [https://github.com/apache/ranger/actions/runs/9719764431/job/26830107611?pr=321]
> Run2: [pass]:
> [https://github.com/apache/ranger/actions/runs/9719764431/job/26831441560]
> CC: [~rmani]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4849) [dependabot] update Python library versions referenced in ranger-tools module
[ https://issues.apache.org/jira/browse/RANGER-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4849: --- Description: This Jira tracks merge of dependent library version updates suggested in following pull requests: * [https://github.com/apache/ranger/pull/182] (Pillows) * [https://github.com/apache/ranger/pull/260] (requests) * [https://github.com/apache/ranger/pull/270] (scipy) * [https://github.com/apache/ranger/pull/275] (certifi) * [https://github.com/apache/ranger/pull/323] (idna) * [https://github.com/apache/ranger/pull/324] (jinja2) * [https://github.com/apache/ranger/pull/325] (urllib3) was: This Jira tracks merge of dependent library version updates suggested in following pull requests: * [https://github.com/apache/ranger/pull/182] (Pillows) * [https://github.com/apache/ranger/pull/260] (requests) * [https://github.com/apache/ranger/pull/270] (scipy) * [https://github.com/apache/ranger/pull/275] (certifi) > [dependabot] update Python library versions referenced in ranger-tools module > - > > Key: RANGER-4849 > URL: https://issues.apache.org/jira/browse/RANGER-4849 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Attachments: RANGER-4849.patch > > > This Jira tracks merge of dependent library version updates suggested in > following pull requests: > * [https://github.com/apache/ranger/pull/182] (Pillows) > * [https://github.com/apache/ranger/pull/260] (requests) > * [https://github.com/apache/ranger/pull/270] (scipy) > * [https://github.com/apache/ranger/pull/275] (certifi) > * [https://github.com/apache/ranger/pull/323] (idna) > * [https://github.com/apache/ranger/pull/324] (jinja2) > * [https://github.com/apache/ranger/pull/325] (urllib3) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4849) [dependabot] Python library versions referenced in ranger-tools module
[ https://issues.apache.org/jira/browse/RANGER-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864422#comment-17864422 ] Abhishek Kumar commented on RANGER-4849: LGTM. +1 > [dependabot] Python library versions referenced in ranger-tools module > -- > > Key: RANGER-4849 > URL: https://issues.apache.org/jira/browse/RANGER-4849 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.5.0 > > Attachments: RANGER-4849.patch > > > This Jira tracks merge of dependent library version updates suggested in > following pull requests: > * [https://github.com/apache/ranger/pull/182] (Pillows) > * [https://github.com/apache/ranger/pull/260] (requests) > * [https://github.com/apache/ranger/pull/270] (scipy) > * [https://github.com/apache/ranger/pull/275] (certifi) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4836) Ranger Usersync failing due to java.lang.NoClassDefFoundError
[
https://issues.apache.org/jira/browse/RANGER-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860978#comment-17860978
]
Abhishek Kumar commented on RANGER-4836:
Merged in
[master|https://github.com/apache/ranger/commit/01882a82550ad9b180b2deeedb402f9712254ed3]
> Ranger Usersync failing due to java.lang.NoClassDefFoundError
> -
>
> Key: RANGER-4836
> URL: https://issues.apache.org/jira/browse/RANGER-4836
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
>
> It appears that introduction of jackson fasterxml libraries cause the
> following error to be seen in usersync logs:
> {code:java}
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/type/TypeReference
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildGroupList(PolicyMgrUserGroupBuilder.java:463)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildUserGroupInfo(PolicyMgrUserGroupBuilder.java:426)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.init(PolicyMgrUserGroupBuilder.java:240)
> at
> org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:50)
> at java.lang.Thread.run(Thread.java:750)
> Caused by: java.lang.ClassNotFoundException:
> com.fasterxml.jackson.core.type.TypeReference
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 5 common frames omitted
> 28 Jun 2024 19:10:28 DEBUG o.a.r.u.UserGroupSync [UnixUserSyncThread] -
> Sleeping for [6] milliSeconds {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4836) Ranger Usersync failing due to java.lang.NoClassDefFoundError
[
https://issues.apache.org/jira/browse/RANGER-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4836:
---
Affects Version/s: 2.5.0
> Ranger Usersync failing due to java.lang.NoClassDefFoundError
> -
>
> Key: RANGER-4836
> URL: https://issues.apache.org/jira/browse/RANGER-4836
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 2.5.0
>
>
> It appears that introduction of jackson fasterxml libraries cause the
> following error to be seen in usersync logs:
> {code:java}
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/type/TypeReference
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildGroupList(PolicyMgrUserGroupBuilder.java:463)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildUserGroupInfo(PolicyMgrUserGroupBuilder.java:426)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.init(PolicyMgrUserGroupBuilder.java:240)
> at
> org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:50)
> at java.lang.Thread.run(Thread.java:750)
> Caused by: java.lang.ClassNotFoundException:
> com.fasterxml.jackson.core.type.TypeReference
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 5 common frames omitted
> 28 Jun 2024 19:10:28 DEBUG o.a.r.u.UserGroupSync [UnixUserSyncThread] -
> Sleeping for [6] milliSeconds {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4836) Ranger Usersync failing due to java.lang.NoClassDefFoundError
[
https://issues.apache.org/jira/browse/RANGER-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4836:
---
Fix Version/s: 3.0.0
> Ranger Usersync failing due to java.lang.NoClassDefFoundError
> -
>
> Key: RANGER-4836
> URL: https://issues.apache.org/jira/browse/RANGER-4836
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 3.0.0, 2.5.0
>
>
> It appears that introduction of jackson fasterxml libraries cause the
> following error to be seen in usersync logs:
> {code:java}
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/type/TypeReference
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildGroupList(PolicyMgrUserGroupBuilder.java:463)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildUserGroupInfo(PolicyMgrUserGroupBuilder.java:426)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.init(PolicyMgrUserGroupBuilder.java:240)
> at
> org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:50)
> at java.lang.Thread.run(Thread.java:750)
> Caused by: java.lang.ClassNotFoundException:
> com.fasterxml.jackson.core.type.TypeReference
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 5 common frames omitted
> 28 Jun 2024 19:10:28 DEBUG o.a.r.u.UserGroupSync [UnixUserSyncThread] -
> Sleeping for [6] milliSeconds {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (RANGER-4836) Ranger Usersync failing due to java.lang.NoClassDefFoundError
[
https://issues.apache.org/jira/browse/RANGER-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-4836.
Fix Version/s: 2.5.0
Resolution: Fixed
> Ranger Usersync failing due to java.lang.NoClassDefFoundError
> -
>
> Key: RANGER-4836
> URL: https://issues.apache.org/jira/browse/RANGER-4836
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 2.5.0
>
>
> It appears that introduction of jackson fasterxml libraries cause the
> following error to be seen in usersync logs:
> {code:java}
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/type/TypeReference
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildGroupList(PolicyMgrUserGroupBuilder.java:463)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildUserGroupInfo(PolicyMgrUserGroupBuilder.java:426)
> at
> org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.init(PolicyMgrUserGroupBuilder.java:240)
> at
> org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:50)
> at java.lang.Thread.run(Thread.java:750)
> Caused by: java.lang.ClassNotFoundException:
> com.fasterxml.jackson.core.type.TypeReference
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 5 common frames omitted
> 28 Jun 2024 19:10:28 DEBUG o.a.r.u.UserGroupSync [UnixUserSyncThread] -
> Sleeping for [6] milliSeconds {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4837) Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
[
https://issues.apache.org/jira/browse/RANGER-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4837:
---
Description:
Below is the intermittent test failure observed:
{code:java}
2024-06-29T00:04:41.5790918Z Tests run: 12, Failures: 1, Errors: 0, Skipped: 0,
Time elapsed: 627.963 sec <<< FAILURE! - in
org.apache.ranger.audit.TestAuditQueue
2024-06-29T00:04:41.5800847Z
testAuditFileQueueSpoolORCRollover(org.apache.ranger.audit.TestAuditQueue)
Time elapsed: 549.462 sec <<< FAILURE!
2024-06-29T00:04:41.5802113Z java.lang.AssertionError: File created
2024-06-29T00:04:41.5870847Zat org.junit.Assert.fail(Assert.java:89)
2024-06-29T00:04:41.5871624Zat org.junit.Assert.assertTrue(Assert.java:42)
2024-06-29T00:04:41.5875524Zat
org.apache.ranger.audit.TestAuditQueue.testAuditFileQueueSpoolORCRollover(TestAuditQueue.java:804)
{code}
Run1: [failure]:
[https://github.com/apache/ranger/actions/runs/9719764431/job/26830107611?pr=321]
Run2: [pass]:
[https://github.com/apache/ranger/actions/runs/9719764431/job/26831441560]
CC: [~rmani]
was:
Below is the intermittent test failure observed:
{code:java}
2024-06-29T00:04:41.5790918Z Tests run: 12, Failures: 1, Errors: 0, Skipped: 0,
Time elapsed: 627.963 sec <<< FAILURE! - in
org.apache.ranger.audit.TestAuditQueue
2024-06-29T00:04:41.5800847Z
testAuditFileQueueSpoolORCRollover(org.apache.ranger.audit.TestAuditQueue)
Time elapsed: 549.462 sec <<< FAILURE!
2024-06-29T00:04:41.5802113Z java.lang.AssertionError: File created
2024-06-29T00:04:41.5870847Zat org.junit.Assert.fail(Assert.java:89)
2024-06-29T00:04:41.5871624Zat org.junit.Assert.assertTrue(Assert.java:42)
2024-06-29T00:04:41.5875524Zat
org.apache.ranger.audit.TestAuditQueue.testAuditFileQueueSpoolORCRollover(TestAuditQueue.java:804)
{code}
Run1: [failure]:
[https://github.com/apache/ranger/actions/runs/9719764431/job/26830107611?pr=321]
Run2: [pass]:
[https://github.com/apache/ranger/actions/runs/9719764431/job/26831441560]
> Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
>
>
> Key: RANGER-4837
> URL: https://issues.apache.org/jira/browse/RANGER-4837
> Project: Ranger
> Issue Type: Bug
> Components: audit
>Affects Versions: 2.5.0
>Reporter: Abhishek Kumar
>Priority: Major
>
> Below is the intermittent test failure observed:
> {code:java}
> 2024-06-29T00:04:41.5790918Z Tests run: 12, Failures: 1, Errors: 0, Skipped:
> 0, Time elapsed: 627.963 sec <<< FAILURE! - in
> org.apache.ranger.audit.TestAuditQueue
> 2024-06-29T00:04:41.5800847Z
> testAuditFileQueueSpoolORCRollover(org.apache.ranger.audit.TestAuditQueue)
> Time elapsed: 549.462 sec <<< FAILURE!
> 2024-06-29T00:04:41.5802113Z java.lang.AssertionError: File created
> 2024-06-29T00:04:41.5870847Z at org.junit.Assert.fail(Assert.java:89)
> 2024-06-29T00:04:41.5871624Z at org.junit.Assert.assertTrue(Assert.java:42)
> 2024-06-29T00:04:41.5875524Z at
> org.apache.ranger.audit.TestAuditQueue.testAuditFileQueueSpoolORCRollover(TestAuditQueue.java:804)
> {code}
> Run1: [failure]:
> [https://github.com/apache/ranger/actions/runs/9719764431/job/26830107611?pr=321]
> Run2: [pass]:
> [https://github.com/apache/ranger/actions/runs/9719764431/job/26831441560]
> CC: [~rmani]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4837) Intermittent test failures in org.apache.ranger.audit.TestAuditQueue
Abhishek Kumar created RANGER-4837:
--
Summary: Intermittent test failures in
org.apache.ranger.audit.TestAuditQueue
Key: RANGER-4837
URL: https://issues.apache.org/jira/browse/RANGER-4837
Project: Ranger
Issue Type: Bug
Components: audit
Affects Versions: 2.5.0
Reporter: Abhishek Kumar
Below is the intermittent test failure observed:
{code:java}
2024-06-29T00:04:41.5790918Z Tests run: 12, Failures: 1, Errors: 0, Skipped: 0,
Time elapsed: 627.963 sec <<< FAILURE! - in
org.apache.ranger.audit.TestAuditQueue
2024-06-29T00:04:41.5800847Z
testAuditFileQueueSpoolORCRollover(org.apache.ranger.audit.TestAuditQueue)
Time elapsed: 549.462 sec <<< FAILURE!
2024-06-29T00:04:41.5802113Z java.lang.AssertionError: File created
2024-06-29T00:04:41.5870847Zat org.junit.Assert.fail(Assert.java:89)
2024-06-29T00:04:41.5871624Zat org.junit.Assert.assertTrue(Assert.java:42)
2024-06-29T00:04:41.5875524Zat
org.apache.ranger.audit.TestAuditQueue.testAuditFileQueueSpoolORCRollover(TestAuditQueue.java:804)
{code}
Run1: [failure]:
[https://github.com/apache/ranger/actions/runs/9719764431/job/26830107611?pr=321]
Run2: [pass]:
[https://github.com/apache/ranger/actions/runs/9719764431/job/26831441560]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4836) Ranger Usersync failing due to java.lang.NoClassDefFoundError
Abhishek Kumar created RANGER-4836:
--
Summary: Ranger Usersync failing due to
java.lang.NoClassDefFoundError
Key: RANGER-4836
URL: https://issues.apache.org/jira/browse/RANGER-4836
Project: Ranger
Issue Type: Bug
Components: usersync
Reporter: Abhishek Kumar
Assignee: Abhishek Kumar
It appears that introduction of jackson fasterxml libraries cause the following
error to be seen in usersync logs:
{code:java}
java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/type/TypeReference
at
org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildGroupList(PolicyMgrUserGroupBuilder.java:463)
at
org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.buildUserGroupInfo(PolicyMgrUserGroupBuilder.java:426)
at
org.apache.ranger.unixusersync.process.PolicyMgrUserGroupBuilder.init(PolicyMgrUserGroupBuilder.java:240)
at
org.apache.ranger.usergroupsync.UserGroupSync.run(UserGroupSync.java:50)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.ClassNotFoundException:
com.fasterxml.jackson.core.type.TypeReference
at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
... 5 common frames omitted
28 Jun 2024 19:10:28 DEBUG o.a.r.u.UserGroupSync [UnixUserSyncThread] -
Sleeping for [6] milliSeconds {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4818) [usersync] Users undergoing role reset to ROLE_USER from ROLE_SYS_ADMIN
[ https://issues.apache.org/jira/browse/RANGER-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4818: --- Description: updateUserRoleAssignments function in XUserMgr (ranger-admin) resets the role of the user from admin to user role for users which are part of the request but are not part of the same page when paged requests are sent to ranger-admin from ranger-usersync. (was: updateRoleAssignments on ranger-admin resets the role of the user from admin to user role for users which are part of the request but are not part of the same page when paged requests are sent to ranger-admin from ranger-usersync.) > [usersync] Users undergoing role reset to ROLE_USER from ROLE_SYS_ADMIN > --- > > Key: RANGER-4818 > URL: https://issues.apache.org/jira/browse/RANGER-4818 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > updateUserRoleAssignments function in XUserMgr (ranger-admin) resets the role > of the user from admin to user role for users which are part of the request > but are not part of the same page when paged requests are sent to > ranger-admin from ranger-usersync. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4818) [usersync] Users undergoing role reset to ROLE_USER from ROLE_SYS_ADMIN
Abhishek Kumar created RANGER-4818: -- Summary: [usersync] Users undergoing role reset to ROLE_USER from ROLE_SYS_ADMIN Key: RANGER-4818 URL: https://issues.apache.org/jira/browse/RANGER-4818 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.4.0 Reporter: Abhishek Kumar Assignee: Abhishek Kumar updateRoleAssignments on ranger-admin resets the role of the user from admin to user role for users which are part of the request but are not part of the same page when paged requests are sent to ranger-admin from ranger-usersync. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4511) Enable Parallel Compilation for Multiple Modules in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4511: --- Fix Version/s: 3.0.0 > Enable Parallel Compilation for Multiple Modules in Ranger > -- > > Key: RANGER-4511 > URL: https://issues.apache.org/jira/browse/RANGER-4511 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Fix For: 3.0.0 > > Attachments: image-2023-11-03-11-15-50-593.png, > patch1-RANGER-4511.diff > > Time Spent: 0.5h > Remaining Estimate: 0h > > "Due to incorrect dependency settings in the distro module, Ranger cannot > utilize multicore concurrent compilation. As a result, compiling Ranger is > very slow each time, as all modules can only be compiled serially. > With this patch, Ranger can be compiled in parallel, greatly speeding up the > process. Compilation can now be completed in just a few minutes. > !image-2023-11-03-11-15-50-593.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4746) Clean up modules in ranger-jdk11 profile
[ https://issues.apache.org/jira/browse/RANGER-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829931#comment-17829931 ] Abhishek Kumar commented on RANGER-4746: [Commit|https://github.com/apache/ranger/commit/a1dc8326154d5472c275bd877e4f0fe319c4b995] [PR|https://github.com/apache/ranger/pull/301] > Clean up modules in ranger-jdk11 profile > - > > Key: RANGER-4746 > URL: https://issues.apache.org/jira/browse/RANGER-4746 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > ranger-jdk11 profile is currently used for Trino, this Jira aims to fix the > module structure for the same profile i.e building only the required modules > instead of the full ranger repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4511) Enable Parallel Compilation for Multiple Modules in Ranger
[ https://issues.apache.org/jira/browse/RANGER-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829912#comment-17829912 ] Abhishek Kumar commented on RANGER-4511: [~jialiang] The PR [289|https://github.com/apache/ranger/pull/289] has been merged to master, thank you. Please resolve this jira. > Enable Parallel Compilation for Multiple Modules in Ranger > -- > > Key: RANGER-4511 > URL: https://issues.apache.org/jira/browse/RANGER-4511 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Attachments: image-2023-11-03-11-15-50-593.png, > patch1-RANGER-4511.diff > > Time Spent: 0.5h > Remaining Estimate: 0h > > "Due to incorrect dependency settings in the distro module, Ranger cannot > utilize multicore concurrent compilation. As a result, compiling Ranger is > very slow each time, as all modules can only be compiled serially. > With this patch, Ranger can be compiled in parallel, greatly speeding up the > process. Compilation can now be completed in just a few minutes. > !image-2023-11-03-11-15-50-593.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4746) Clean up modules in ranger-jdk11 profile
[ https://issues.apache.org/jira/browse/RANGER-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reassigned RANGER-4746: -- Assignee: Abhishek Kumar > Clean up modules in ranger-jdk11 profile > - > > Key: RANGER-4746 > URL: https://issues.apache.org/jira/browse/RANGER-4746 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > ranger-jdk11 profile is currently used for Trino, this Jira aims to fix the > module structure for the same profile i.e building only the required modules > instead of the full ranger repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4759) Deprecate REST APIs in XUserREST around VXGroupGroup
Abhishek Kumar created RANGER-4759: -- Summary: Deprecate REST APIs in XUserREST around VXGroupGroup Key: RANGER-4759 URL: https://issues.apache.org/jira/browse/RANGER-4759 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.4.0 Reporter: Abhishek Kumar The APIs in XUserREST should be deprecated as they are not used: - getXGroupGroup - createXGroupGroup - updateXGroupGroup - deleteXGroupGroup - searchXGroupGroups - countXGroupGroups -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4758) XUserRest APIs need new transactions to avoid ranger-admin OOM issues
Abhishek Kumar created RANGER-4758: -- Summary: XUserRest APIs need new transactions to avoid ranger-admin OOM issues Key: RANGER-4758 URL: https://issues.apache.org/jira/browse/RANGER-4758 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.4.0 Reporter: Abhishek Kumar Assignee: Abhishek Kumar These are the REST APIs in XUserRest which require new transactions via TransactionManager to avoid ranger admin from going out of memory: - setXUserRolesByName - updateDeletedGroups - updateDeletedUsers -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4752) Enable JDK 11 and 17 builds on GitHub PRs and merges to master
[ https://issues.apache.org/jira/browse/RANGER-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4752: --- Summary: Enable JDK 11 and 17 builds on GitHub PRs and merges to master (was: Enable JDK 11 builds on GitHub PRs and merges to master) > Enable JDK 11 and 17 builds on GitHub PRs and merges to master > -- > > Key: RANGER-4752 > URL: https://issues.apache.org/jira/browse/RANGER-4752 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > For modules which have a compile time requirement of JDK 11, 17 (for eg: > trino), this Jira tracks the work for enabling jdk11 and jdk17 maven build > whenever there is a code change raised via GitHub PRs or merges to master > occur. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4752) Enable JDK 11 builds on GitHub PRs and merges to master
[ https://issues.apache.org/jira/browse/RANGER-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4752: --- Description: For modules which have a compile time requirement of JDK 11, 17 (for eg: trino), this Jira tracks the work for enabling jdk11 and jdk17 maven build whenever there is a code change raised via GitHub PRs or merges to master occur. (was: For modules which have a compile time requirement of JDK 11(for eg: trino), this Jira tracks the work for enabling jdk11 maven build whenever there is a code change raised via GitHub PRs or merges to master occur.) > Enable JDK 11 builds on GitHub PRs and merges to master > --- > > Key: RANGER-4752 > URL: https://issues.apache.org/jira/browse/RANGER-4752 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > For modules which have a compile time requirement of JDK 11, 17 (for eg: > trino), this Jira tracks the work for enabling jdk11 and jdk17 maven build > whenever there is a code change raised via GitHub PRs or merges to master > occur. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4756) [JDK 11]: NullPointerException in KnoxRangerTest
[ https://issues.apache.org/jira/browse/RANGER-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4756: --- Description: Build URL: [https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304] Error logs: 2024-03-20T18:34:20.3418536Z [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.43 s <<< FAILURE! - in org.apache.ranger.services.knox.KnoxRangerTest 2024-03-20T18:34:20.3420325Z [ERROR] org.apache.ranger.services.knox.KnoxRangerTest Time elapsed: 4.43 s <<< ERROR! 2024-03-20T18:34:20.3421404Z java.lang.NullPointerException 2024-03-20T18:34:20.3422776Zat java.base/sun.security.provider.JavaKeyStore.engineStore(JavaKeyStore.java:588) 2024-03-20T18:34:20.3424228Zat java.base/sun.security.util.KeyStoreDelegator.engineStore(KeyStoreDelegator.java:189) 2024-03-20T18:34:20.3425458Zat java.base/java.security.KeyStore.store(KeyStore.java:1411) 2024-03-20T18:34:20.3427109Zat org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.writeKeyStoreToFile(DefaultKeystoreService.java:503) 2024-03-20T18:34:20.3429428Zat org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addCertForGateway(DefaultKeystoreService.java:194) 2024-03-20T18:34:20.3431887Zat org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addSelfSignedCertForGateway(DefaultKeystoreService.java:166) 2024-03-20T18:34:20.3434326Zat org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addSelfSignedCertForGateway(DefaultKeystoreService.java:160) 2024-03-20T18:34:20.3436370Zat org.apache.knox.gateway.services.security.impl.JettySSLService.init(JettySSLService.java:88) 2024-03-20T18:34:20.3438041Zat org.apache.knox.gateway.services.DefaultGatewayServices.init(DefaultGatewayServices.java:104) 2024-03-20T18:34:20.3439852Zat org.apache.knox.gateway.GatewayTestDriver.setupGateway(GatewayTestDriver.java:162) 2024-03-20T18:34:20.3441313Zat org.apache.ranger.services.knox.KnoxRangerTest.setupSuite(KnoxRangerTest.java:60) 2024-03-20T18:34:20.3442783Zat java.base/java.lang.reflect.Method.invoke(Method.java:566) was: Build URL: [https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304] Error logs: Error: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.43 s <<< FAILURE! - in org.apache.ranger.services.knox.KnoxRangerTest [4264|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4265]Error: org.apache.ranger.services.knox.KnoxRangerTest Time elapsed: 4.43 s <<< ERROR! [4265|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4266]java.lang.NullPointerException [4266|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4267] at java.base/sun.security.provider.JavaKeyStore.engineStore(JavaKeyStore.java:588) [4267|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4268] at java.base/sun.security.util.KeyStoreDelegator.engineStore(KeyStoreDelegator.java:189) [4268|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4269] at java.base/java.security.KeyStore.store(KeyStore.java:1411) [4269|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4270] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.writeKeyStoreToFile(DefaultKeystoreService.java:503) [4270|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4271] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addCertForGateway(DefaultKeystoreService.java:194) [4271|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4272] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addSelfSignedCertForGateway(DefaultKeystoreService.java:166) [4272|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4273] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addSelfSignedCertForGateway(DefaultKeystoreService.java:160) [4273|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4274] at org.apache.knox.gateway.services.security.impl.JettySSLService.init(JettySSLService.java:88) [4274|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4275] at org.apache.knox.gateway.services.DefaultGatewayServices.init(DefaultGatewayServices.java:104) [4275|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4276] at org.apache.knox.gateway.GatewayTestDriver.setupGateway(GatewayTestDriver.java:162) [4276|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:427
[jira] [Created] (RANGER-4756) [JDK 11]: NullPointerException in KnoxRangerTest
Abhishek Kumar created RANGER-4756: -- Summary: [JDK 11]: NullPointerException in KnoxRangerTest Key: RANGER-4756 URL: https://issues.apache.org/jira/browse/RANGER-4756 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Abhishek Kumar Build URL: [https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304] Error logs: Error: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.43 s <<< FAILURE! - in org.apache.ranger.services.knox.KnoxRangerTest [4264|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4265]Error: org.apache.ranger.services.knox.KnoxRangerTest Time elapsed: 4.43 s <<< ERROR! [4265|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4266]java.lang.NullPointerException [4266|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4267] at java.base/sun.security.provider.JavaKeyStore.engineStore(JavaKeyStore.java:588) [4267|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4268] at java.base/sun.security.util.KeyStoreDelegator.engineStore(KeyStoreDelegator.java:189) [4268|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4269] at java.base/java.security.KeyStore.store(KeyStore.java:1411) [4269|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4270] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.writeKeyStoreToFile(DefaultKeystoreService.java:503) [4270|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4271] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addCertForGateway(DefaultKeystoreService.java:194) [4271|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4272] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addSelfSignedCertForGateway(DefaultKeystoreService.java:166) [4272|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4273] at org.apache.knox.gateway.services.security.impl.DefaultKeystoreService.addSelfSignedCertForGateway(DefaultKeystoreService.java:160) [4273|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4274] at org.apache.knox.gateway.services.security.impl.JettySSLService.init(JettySSLService.java:88) [4274|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4275] at org.apache.knox.gateway.services.DefaultGatewayServices.init(DefaultGatewayServices.java:104) [4275|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4276] at org.apache.knox.gateway.GatewayTestDriver.setupGateway(GatewayTestDriver.java:162) [4276|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4277] at org.apache.ranger.services.knox.KnoxRangerTest.setupSuite(KnoxRangerTest.java:60) [4277|https://github.com/apache/ranger/actions/runs/8352270188/job/22898147241?pr=304#step:4:4278] at java.base/java.lang.reflect.Method.invoke(Method.java:566) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4751) Enable docker builds for PRs and merges to master
[ https://issues.apache.org/jira/browse/RANGER-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4751: --- Description: Currently, maven build with tests are part of GitHub PRs and merges to master. This Jira tracks an additional job to build all existing docker images whenever there is a code change or merge. This is an initial ticket, to further ensure code changes don't break docker builds or alter the functionality with running containers. was:Currently, maven build with tests are part of GitHub PRs and merges to master. This Jira tracks an additional job to build all existing docker images whenever there is a code change or merge. > Enable docker builds for PRs and merges to master > - > > Key: RANGER-4751 > URL: https://issues.apache.org/jira/browse/RANGER-4751 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > Currently, maven build with tests are part of GitHub PRs and merges to > master. This Jira tracks an additional job to build all existing docker > images whenever there is a code change or merge. > This is an initial ticket, to further ensure code changes don't break docker > builds or alter the functionality with running containers. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4743) [JDK 11]: Fix ranger admin logging
[ https://issues.apache.org/jira/browse/RANGER-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828128#comment-17828128 ] Abhishek Kumar commented on RANGER-4743: Thanks [~rakeshgupta264], I'll try this out. > [JDK 11]: Fix ranger admin logging > --- > > Key: RANGER-4743 > URL: https://issues.apache.org/jira/browse/RANGER-4743 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Attachments: 0001-RANGER-4743.patch > > > Currently, the ranger-admin logs do not appear when built and run with jdk 11. > Logback and slf4j versions need to be upgraded to fix the above issue. > More info: [https://logback.qos.ch/download.html] > CC: [~rmani] -- This message was sent by Atlassian Jira (v8.20.10#820010)
