[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790402#comment-17790402
]
Pradeep Agrawal commented on RANGER-4562:
-
Without docker case :
1. I tried "mvn clean install" command on a fresh jdk11 cluster and i was able
to reproduce the issue with following error
{code:java}
[INFO] --- frontend-maven-plugin:1.12.1:npm (npm install for tests) @
security-admin-web ---
[INFO] Running 'npm install' in /root/ranger/security-admin/target/jstest
[INFO]
[INFO] > phantomjs-prebuilt@2.1.16 install
/root/ranger/security-admin/target/jstest/node_modules/phantomjs-prebuilt
[INFO] > node install.js
[INFO]
[INFO] PhantomJS not found on PATH
[INFO] Download already available at
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] Verified checksum of previously downloaded file
[INFO] Extracting tar contents (via spawned process)
[INFO] Error extracting archive
[INFO] Phantom installation failed { Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] killed: false,
[INFO] code: 2,
[INFO] signal: null,
[INFO] cmd: 'tar jxf /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2' }
Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] npm WARN security-admin@2.0.0 No description
[INFO] npm WARN security-admin@2.0.0 No repository field.
[INFO] npm WARN security-admin@2.0.0 No license field.
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4
(node_modules/fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 1
[INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node install.js`
[INFO] npm ERR! Exit status 1
[INFO] npm ERR!
[INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16 install script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.
[INFO]
[INFO] npm ERR! A complete log of this run can be found in:
[INFO] npm ERR! /root/.npm/_logs/2023-11-28T07_05_28_779Z-debug.log {code}
2. After understanding above error i installed bzip2 by executing the
[command|https://github.com/apache/ranger/blob/master/build_ranger_using_docker.sh#L69]
3. Executed "mvn clean install" again and it succeeded.
{code:java}
[INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @
security-admin-web ---
[INFO] Skipping because packaging 'war' is not pom.
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.7:report (jacoco-site) @ security-admin-web
---
[INFO] Loading execution data file
/root/ranger/security-admin/target/jacoco.exec
[INFO] Analyzed bundle 'Security Admin Web Application' with 671 classes
[INFO]
[INFO] --- frontend-maven-plugin:1.12.1:karma (karma prd) @ security-admin-web
---
[INFO] Running 'karma start ../../src/test/javascript/karma-prd.conf.js' in
/root/ranger/security-admin/target/jstest
[INFO] 28 11 2023 06:32:51.840:INFO [karma-server]: Karma v3.1.4 server started
at http://0.0.0.0:9877/
[INFO] 28 11 2023 06:32:51.842:INFO [launcher]: Launching browsers PhantomJS
with concurrency unlimited
[INFO] 28 11 2023 06:32:51.863:INFO [launcher]: Starting browser PhantomJS
[INFO] 28 11 2023 06:32:51.951:ERROR [phantomjs.launcher]: Fontconfig warning:
ignoring UTF-8: not a valid region tag
[INFO]
[INFO] 28 11 2023 06:32:52.079:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected
on socket MuRdJUviuc4-IMkX with id 77739149
LOG: 'just
[jira] [Comment Edited] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790402#comment-17790402
]
Pradeep Agrawal edited comment on RANGER-4562 at 11/28/23 7:29 AM:
---
Without docker case :
1. I tried "mvn clean install" command on a fresh jdk11 cluster and i was able
to reproduce the issue with following error
{code:java}
[INFO] --- frontend-maven-plugin:1.12.1:npm (npm install for tests) @
security-admin-web ---
[INFO] Running 'npm install' in /root/ranger/security-admin/target/jstest
[INFO]
[INFO] > phantomjs-prebuilt@2.1.16 install
/root/ranger/security-admin/target/jstest/node_modules/phantomjs-prebuilt
[INFO] > node install.js
[INFO]
[INFO] PhantomJS not found on PATH
[INFO] Download already available at
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] Verified checksum of previously downloaded file
[INFO] Extracting tar contents (via spawned process)
[INFO] Error extracting archive
[INFO] Phantom installation failed { Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] killed: false,
[INFO] code: 2,
[INFO] signal: null,
[INFO] cmd: 'tar jxf /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2' }
Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] npm WARN security-admin@2.0.0 No description
[INFO] npm WARN security-admin@2.0.0 No repository field.
[INFO] npm WARN security-admin@2.0.0 No license field.
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4
(node_modules/fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 1
[INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node install.js`
[INFO] npm ERR! Exit status 1
[INFO] npm ERR!
[INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16 install script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.
[INFO]
[INFO] npm ERR! A complete log of this run can be found in:
[INFO] npm ERR! /root/.npm/_logs/2023-11-28T07_05_28_779Z-debug.log {code}
2. After understanding above error i installed bzip2 by executing the
[command|https://github.com/apache/ranger/blob/master/build_ranger_using_docker.sh#L69]
3. Executed "mvn clean install" again and it succeeded.
{code:java}
[INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @
security-admin-web ---
[INFO] Skipping because packaging 'war' is not pom.
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.7:report (jacoco-site) @ security-admin-web
---
[INFO] Loading execution data file
/root/ranger/security-admin/target/jacoco.exec
[INFO] Analyzed bundle 'Security Admin Web Application' with 671 classes
[INFO]
[INFO] --- frontend-maven-plugin:1.12.1:karma (karma prd) @ security-admin-web
---
[INFO] Running 'karma start ../../src/test/javascript/karma-prd.conf.js' in
/root/ranger/security-admin/target/jstest
[INFO] 28 11 2023 06:32:51.840:INFO [karma-server]: Karma v3.1.4 server started
at http://0.0.0.0:9877/
[INFO] 28 11 2023 06:32:51.842:INFO [launcher]: Launching browsers PhantomJS
with concurrency unlimited
[INFO] 28 11 2023 06:32:51.863:INFO [launcher]: Starting browser PhantomJS
[INFO] 28 11 2023 06:32:51.951:ERROR [phantomjs.launcher]: Fontconfig warning:
ignoring UTF-8: not a valid region tag
[INFO]
[INFO] 28 11 2023 06:32:52.079:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected
on socket
Re: Review Request 74755: RANGER-4558 : User is allowed to create/update sharedResource, even if the user is not zoneAdmin in the linked dataShared
> On Nov. 25, 2023, 8:17 a.m., Madhan Neethiraj wrote: > > > 5)Expected : The current user should be zoneAdmin as well as dataShare > > > Admin to create/upadate shared Resource > > > > Prashant - user with one of the following privileges should be allowed to > > create/update/delete shared-resources in a dataShare > > - Datashare admin > > - Zone admin > > - Service admin > > - Ranger admin > > Madhan Neethiraj wrote: > Prashant - please ignore my earlier comment. Here is the requirement: > > 1. add/update shared resource: will require admin privilege on **both** > dataShare and one of zone/service/Ranger > 2. remove a shared resource: will require admin privilege on **either** > dataShare or one of zone/service/Ranger > > Please make sure this patch addressed both #1 and #2. Thanks! have made changes as suggested in comment please review - Prashant --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74755/#review226001 --- On Nov. 28, 2023, 7:09 a.m., Prashant Satam wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74755/ > --- > > (Updated Nov. 28, 2023, 7:09 a.m.) > > > Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, > Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale. > > > Bugs: RANGER-4558 > https://issues.apache.org/jira/browse/RANGER-4558 > > > Repository: ranger > > > Description > --- > > User should be zoneAdmin along with datashare admin of linked sharedResource > to create/update > > Steps to check >1)Create SecurityZone >2)Create dataShare link SecurityZone to it >3)Current user is only zoneAdmin not datashare admin >4)Current User is able to create/upadate shared Resource >5)Expected : The current user should be zoneAdmin as well as dataShare > Admin to create/upadate shared Resource > > > Diffs > - > > > security-admin/src/main/java/org/apache/ranger/validation/RangerGdsValidator.java > 178c8f0e2 > > > Diff: https://reviews.apache.org/r/74755/diff/2/ > > > Testing > --- > > Steps to Check > 1)Create SecurityZone > 2)Create dataShare link SecurityZone to it > 3)Current user is zoneAdmin and datashare admin > 4)Current User is able to create/upadate shared Resource > > > Thanks, > > Prashant Satam > >
Re: Review Request 74755: RANGER-4558 : User is allowed to create/update sharedResource, even if the user is not zoneAdmin in the linked dataShared
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74755/ --- (Updated Nov. 28, 2023, 7:09 a.m.) Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale. Bugs: RANGER-4558 https://issues.apache.org/jira/browse/RANGER-4558 Repository: ranger Description --- User should be zoneAdmin along with datashare admin of linked sharedResource to create/update Steps to check 1)Create SecurityZone 2)Create dataShare link SecurityZone to it 3)Current user is only zoneAdmin not datashare admin 4)Current User is able to create/upadate shared Resource 5)Expected : The current user should be zoneAdmin as well as dataShare Admin to create/upadate shared Resource Diffs (updated) - security-admin/src/main/java/org/apache/ranger/validation/RangerGdsValidator.java 178c8f0e2 Diff: https://reviews.apache.org/r/74755/diff/2/ Changes: https://reviews.apache.org/r/74755/diff/1-2/ Testing --- Steps to Check 1)Create SecurityZone 2)Create dataShare link SecurityZone to it 3)Current user is zoneAdmin and datashare admin 4)Current User is able to create/upadate shared Resource Thanks, Prashant Satam
[jira] [Commented] (RANGER-4370) [Ranger UI] [React JS]"Select All permissions for all components." checkbox missing in tag based policy permission popup
[
https://issues.apache.org/jira/browse/RANGER-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790365#comment-17790365
]
Brijesh Bhalala commented on RANGER-4370:
-
Commited to [Apache
master|https://github.com/apache/ranger/commit/98558adc98b604e6ee6371a28eaebdb0cf4508f5]
branch
> [Ranger UI] [React JS]"Select All permissions for all components." checkbox
> missing in tag based policy permission popup
>
>
> Key: RANGER-4370
> URL: https://issues.apache.org/jira/browse/RANGER-4370
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Minor
> Labels: ranger-react
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4370.patch, 0002-RANGER-4370.patch,
> 0003-RANGER-4370.patch
>
>
> {color:#172b4d}In the permissions selector popup for tag based policies in
> Backbone UI,{color}
> {color:#172b4d}there is a checkbox which allows users to select all
> permissions for all components selected.{color}
> {color:#172b4d}But in React UI, this checkbox is missing.{color}
> {color:#172b4d}This is a minor bug.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74405: RANGER-4195:Exposing the Ranger REST API is used to fetch the health check status of Ranger Admin
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74405/
---
(Updated Nov. 28, 2023, 3:19 a.m.)
Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj,
Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj,
Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy.
Bugs: RANGER-4195
https://issues.apache.org/jira/browse/RANGER-4195
Repository: ranger
Description (updated)
---
Exposing the Ranger REST API is used to fetch the health check status of Ranger
Admin
RangerAdmin Health Check JSON Response look like (In the current implementation)
{
"status": "UP",
"components": {
"db": {
"status": "UP",
"details":
{ "database": "Oracle 21.3c", "validationQuery": "SELECT banner from v$version
where rownum<2" }
}
}
}
In the future we can extend this health check API for other components like
AuditHandler (Elastic search, Kafka,HDFS, Solr),KMS ,etc
Another Example :
{
"status": "UP",
"components": {
"db": {
"status": "UP",
"details":
{ "database": "Oracle 21.3c", "validationQuery": "SELECT banner from v$version
where rownum<2" }
},
"auditProvider": {
"status": "UP",
"details":
{ "provider": "Elastic Search", "providerHealthCheckEndpoint":
"http://localhost:9200/_cluster/health?pretty; }
}
}
}
As part of this PR ,we have added some refactoring stuffs as well.
For SUPPORTS, Spring first checks if an active transaction exists. If a
transaction exists, then the existing transaction will be used. If there isn’t
a transaction, it is executed non-transactional
NOT_SUPPORTED Propagation
If a current transaction exists, first Spring suspends it, and then the
business logic is executed without a transaction:
For more info:
https://www.javainuse.com/spring/boot-transaction-propagation
https://levelup.gitconnected.com/mastering-transaction-propagation-in-spring-boot-ensure-data-consistency-and-integrity-across-ab9f1a8aa245
Diffs
-
agents-audit/src/main/java/org/apache/ranger/audit/provider/AuditProviderFactory.java
598659bf4
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerServerHealth.java
PRE-CREATION
agents-common/src/test/java/org/apache/ranger/plugin/model/TestRangerHealth.java
PRE-CREATION
security-admin/src/main/java/org/apache/ranger/biz/RangerBizUtil.java
136a1309b
security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java
cd92d92b4
security-admin/src/main/java/org/apache/ranger/common/db/BaseDao.java
a0ff18948
security-admin/src/main/java/org/apache/ranger/patch/cliutil/MetricUtil.java
7d4828ed0
security-admin/src/main/java/org/apache/ranger/rest/RangerHealthREST.java
PRE-CREATION
security-admin/src/main/java/org/apache/ranger/util/RangerServerHealthUtil.java
PRE-CREATION
security-admin/src/main/resources/conf.dist/security-applicationContext.xml
807791f28
security-admin/src/test/java/org/apache/ranger/biz/TestRangerBizUtil.java
22e290a66
security-admin/src/test/java/org/apache/ranger/rest/TestRangerHealthREST.java
PRE-CREATION
security-admin/src/test/java/org/apache/ranger/util/TestRangerServerHealthUtil.java
PRE-CREATION
Diff: https://reviews.apache.org/r/74405/diff/6/
Testing
---
Tested this API and the response below
{"status":"UP","details":{"components":{"db":{"details":{"database":"ORACLE
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 -
Production","validationQuery":"SELECT banner from v$version where
rownum<2"},"status":"UP"
Thanks,
Ramachandran Krishnan
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790198#comment-17790198
]
Madhan Neethiraj commented on RANGER-4562:
--
[~pradeep] - the same failure with 1.11.3 as well.
{noformat}
ranger-build | [INFO] --- frontend-maven-plugin:1.11.3:npm (npm install for
tests) @ security-admin-web ---
ranger-build | [INFO] Running 'npm install' in
/home/ranger/src/security-admin/target/jstest
ranger-build | [INFO]
ranger-build | [INFO] > phantomjs-prebuilt@2.1.16 install
/home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
ranger-build | [INFO] > node install.js
ranger-build | [INFO]
ranger-build | [INFO] PhantomJS not found on PATH
ranger-build | [INFO] Unexpected platform or architecture: linux/arm64
ranger-build | [INFO] It seems there is no binary available for your
platform/architecture
ranger-build | [INFO] Try to install PhantomJS globally
ranger-build | [INFO] npm WARN security-admin@2.0.0 No description
ranger-build | [INFO] npm WARN security-admin@2.0.0 No repository field.
ranger-build | [INFO] npm WARN security-admin@2.0.0 No license field.
ranger-build | [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
fsevents@1.2.4 (node_modules/fsevents):
ranger-build | [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
(current: {"os":"linux","arch":"arm64"})
ranger-build | [INFO]
ranger-build | [INFO] npm ERR! code ELIFECYCLE
ranger-build | [INFO] npm ERR! errno 1
ranger-build | [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
install.js`
ranger-build | [INFO] npm ERR! Exit status 1
ranger-build | [INFO] npm ERR!
ranger-build | [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16 install
script.
ranger-build | [INFO] npm ERR! This is probably not a problem with npm. There
is likely additional logging output above.
ranger-build | [INFO]
ranger-build | [INFO] npm ERR! A complete log of this run can be found in:
ranger-build | [INFO] npm ERR!
/home/ranger/.npm/_logs/2023-11-27T17_47_11_223Z-debug.log
ranger-build | [INFO]
{noformat}
Here are the steps to reproduce this issue:
# {{cd dev-support/ranger-docker}}
# Edit file .env to set {{SKIPTESTS=false}}
# Build Ranger using docker with the following command:
{{docker-compose -f docker-compose.ranger-base.yml -f
docker-compose.ranger-build.yml up}}
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build|
[jira] [Comment Edited] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790183#comment-17790183
]
Pradeep Agrawal edited comment on RANGER-4562 at 11/27/23 5:14 PM:
---
[~madhan]
Can you try with version
[1.11.3|https://mvnrepository.com/artifact/com.github.eirslett/frontend-maven-plugin/1.11.3]
here in security-admin/pom.xml file
[https://github.com/apache/ranger/blob/master/security-admin/pom.xml#L1043]
was (Author: pradeep.agrawal):
[~madhan]
Can you try with version 1.11.3 here in security-admin/pom.xml file
[https://github.com/apache/ranger/blob/master/security-admin/pom.xml#L1043]
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790183#comment-17790183
]
Pradeep Agrawal commented on RANGER-4562:
-
[~madhan]
Can you try with version 1.11.3 here in security-admin/pom.xml file
[https://github.com/apache/ranger/blob/master/security-admin/pom.xml#L1043]
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790181#comment-17790181
]
Madhan Neethiraj commented on RANGER-4562:
--
[~pradeep] - build fails even without {{-Pranger-jdk11}} option - see below.
Btw, build in Apache uses the command-line given in the description, which
includes {{{}-Pranger-jdk11{}}}.
{noformat}
ranger-build | [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install for
tests) @ security-admin-web ---
ranger-build | [INFO] Running 'npm install' in
/home/ranger/src/security-admin/target/jstest
ranger-build | [INFO]
ranger-build | [INFO] > phantomjs-prebuilt@2.1.16 install
/home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
ranger-build | [INFO] > node install.js
ranger-build | [INFO]
ranger-build | [INFO] PhantomJS not found on PATH
ranger-build | [INFO] Unexpected platform or architecture: linux/arm64
ranger-build | [INFO] It seems there is no binary available for your
platform/architecture
ranger-build | [INFO] Try to install PhantomJS globally
ranger-build | [INFO] npm WARN security-admin@2.0.0 No description
ranger-build | [INFO] npm WARN security-admin@2.0.0 No repository field.
ranger-build | [INFO] npm WARN security-admin@2.0.0 No license field.
ranger-build | [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
fsevents@1.2.4 (node_modules/fsevents):
ranger-build | [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
(current: {"os":"linux","arch":"arm64"})
ranger-build | [INFO]
ranger-build | [INFO] npm ERR! code ELIFECYCLE
ranger-build | [INFO] npm ERR! errno 1
ranger-build | [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
install.js`
ranger-build | [INFO] npm ERR! Exit status 1
ranger-build | [INFO] npm ERR!
ranger-build | [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16 install
script.
ranger-build | [INFO] npm ERR! This is probably not a problem with npm. There
is likely additional logging output above.
ranger-build | [INFO]
ranger-build | [INFO] npm ERR! A complete log of this run can be found in:
ranger-build | [INFO] npm ERR!
/home/ranger/.npm/_logs/2023-11-27T17_04_31_708Z-debug.log
{noformat}
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR!
Re: Review Request 74405: RANGER-4195:Exposing the Ranger REST API is used to fetch the health check status of Ranger Admin
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74405/
---
(Updated Nov. 27, 2023, 4:27 p.m.)
Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj,
Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj,
Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy.
Bugs: RANGER-4195
https://issues.apache.org/jira/browse/RANGER-4195
Repository: ranger
Description (updated)
---
Exposing the Ranger REST API is used to fetch the health check status of Ranger
Admin
RangerAdmin Health Check JSON Response look like (In the current implementation)
{
"status": "UP",
"components": {
"db": {
"status": "UP",
"details":
{ "database": "Oracle 21.3c", "validationQuery": "SELECT banner from v$version
where rownum<2" }
}
}
}
In the future we can extend this health check API for other components like
AuditHandler (Elastic search, Kafka,HDFS, Solr),KMS ,etc
Another Example :
{
"status": "UP",
"components": {
"db": {
"status": "UP",
"details":
{ "database": "Oracle 21.3c", "validationQuery": "SELECT banner from v$version
where rownum<2" }
},
"auditProvider": {
"status": "UP",
"details":
{ "provider": "Elastic Search", "providerHealthCheckEndpoint":
"http://localhost:9200/_cluster/health?pretty; }
}
}
}
As part of this PR ,we have added some refactoring stuffs as well.
For SUPPORTS, Spring first checks if an active transaction exists. If a
transaction exists, then the existing transaction will be used. If there isn’t
a transaction, it is executed non-transactional
NOT_SUPPORTED Propagation
If a current transaction exists, first Spring suspends it, and then the
business logic is executed without a transaction:
For more info:
https://www.javainuse.com/spring/boot-transaction-propagation
https://levelup.gitconnected.com/mastering-transaction-propagation-in-spring-boot-ensure-data-consistency-and-integrity-across-ab9f1a8aa245
Diffs (updated)
-
agents-audit/src/main/java/org/apache/ranger/audit/provider/AuditProviderFactory.java
598659bf4
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerServerHealth.java
PRE-CREATION
agents-common/src/test/java/org/apache/ranger/plugin/model/TestRangerHealth.java
PRE-CREATION
security-admin/src/main/java/org/apache/ranger/biz/RangerBizUtil.java
136a1309b
security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java
cd92d92b4
security-admin/src/main/java/org/apache/ranger/common/db/BaseDao.java
a0ff18948
security-admin/src/main/java/org/apache/ranger/patch/cliutil/MetricUtil.java
7d4828ed0
security-admin/src/main/java/org/apache/ranger/rest/RangerHealthREST.java
PRE-CREATION
security-admin/src/main/java/org/apache/ranger/util/RangerServerHealthUtil.java
PRE-CREATION
security-admin/src/main/resources/conf.dist/security-applicationContext.xml
807791f28
security-admin/src/test/java/org/apache/ranger/biz/TestRangerBizUtil.java
22e290a66
security-admin/src/test/java/org/apache/ranger/rest/TestRangerHealthREST.java
PRE-CREATION
security-admin/src/test/java/org/apache/ranger/util/TestRangerServerHealthUtil.java
PRE-CREATION
Diff: https://reviews.apache.org/r/74405/diff/6/
Changes: https://reviews.apache.org/r/74405/diff/5-6/
Testing
---
Tested this API and the response below
{"status":"UP","details":{"components":{"db":{"details":{"database":"ORACLE
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 -
Production","validationQuery":"SELECT banner from v$version where
rownum<2"},"status":"UP"
Thanks,
Ramachandran Krishnan
Re: Review Request 74758: RANGER-4560:Ranger Roles Cache improvement to reduce DB calls to the Database
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74758/ --- (Updated Nov. 27, 2023, 3:19 p.m.) Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nikhil P, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy. Summary (updated) - RANGER-4560:Ranger Roles Cache improvement to reduce DB calls to the Database Bugs: RANGER-4560 https://issues.apache.org/jira/browse/RANGER-4560 Repository: ranger Description --- How Ranger uses the Roles Cache (In-Memory) When the lastKnownRoleVersion and rangerRoleVersionInDB are equal then return null. Because roles have not changed since the last time otherwise, It will fetch the roles from the Database update the cache, and then return roles to the User/Ranger Plugins As part of Ranger Roles Cache improvement, we have added the below logic When the rolesVersionInDB and cachedRolesVersion are equal then return cached RangerRoles.Because RangerRoles have not changed since the last time we fetched How it will improve the Ranger Roles Cache When the user/Client(Ranger Plugin) sends the lastKnownRoleVersion as -1 or null, Ranger Roles Cache internally check whether rolesVersionInDB and cachedRolesVersion are equal or not ?. If it equal means, it will fetch it from the Cache rather than fetching the roles from the database update the cache, and then return roles to the User/Ranger Plugins Diffs - security-admin/src/main/java/org/apache/ranger/common/RangerRoleCache.java 933104a16 Diff: https://reviews.apache.org/r/74758/diff/1/ Testing --- Thanks, Ramachandran Krishnan
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790098#comment-17790098
]
Pradeep Agrawal commented on RANGER-4562:
-
[~madhan] :
Are you planning to build Ranger with trino plugin. It seems
[commit|https://github.com/apache/ranger/commit/c51bc9fad8b0897c067dd9c392709120fd87265e]
introduced ranger-jdk11 profile.
or
If you are planning to build Ranger with jdk11 only(without trino) then can you
run your command without "-Pranger-jdk11" option and post the error if any.
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4555) Response metrics for /assets/assets API not proper
[
https://issues.apache.org/jira/browse/RANGER-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4555:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /assets/assets API not proper
> --
>
> Key: RANGER-4555
> URL: https://issues.apache.org/jira/browse/RANGER-4555
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to /assets/assets API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of assets (the
> value returned by /assets/assets/count API is proper).
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4547) The reponse metrics (pagination values) for the /assets/ugsyncAudits/{sync_source} API is not proper
[
https://issues.apache.org/jira/browse/RANGER-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4547:
---
Assignee: Pradeep Agrawal
> The reponse metrics (pagination values) for the
> /assets/ugsyncAudits/{sync_source} API is not proper
>
>
> Key: RANGER-4547
> URL: https://issues.apache.org/jira/browse/RANGER-4547
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the /assets/ugsyncAudits/\{sync_source} API,
> the metrics like total count, result size is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215450040,"vxUgsyncAuditInfoList": [{
> {code}
> Ideally, it should reflect the total number of audits.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4553) Response metrics for /xaudit/trx_log not proper
[
https://issues.apache.org/jira/browse/RANGER-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4553:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /xaudit/trx_log not proper
> ---
>
> Key: RANGER-4553
> URL: https://issues.apache.org/jira/browse/RANGER-4553
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to /xaudit/trx_log API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 200,"totalCount": 0,
> "resultSize": 0,"queryTimeMS": 1700214070565, ...} {code}
> Ideally, the total count value should reflect the total number of logs
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4554) Response metrics for /assets/resources not proper
[
https://issues.apache.org/jira/browse/RANGER-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4554:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /assets/resources not proper
> -
>
> Key: RANGER-4554
> URL: https://issues.apache.org/jira/browse/RANGER-4554
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to /assets/resources API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of resources
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4550) API request to /assets/resource/{id} returns no response
[
https://issues.apache.org/jira/browse/RANGER-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4550:
---
Assignee: Pradeep Agrawal
> API request to /assets/resource/{id} returns no response
>
>
> Key: RANGER-4550
> URL: https://issues.apache.org/jira/browse/RANGER-4550
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the API endpoint /assets/resource/\{id}, no
> response is returned and the status code is 204 No response.
> Ideally, the response should contain the details for the resource with the
> given id
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4549) Non admin users cannot access /public/v2/api/roles/names and /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
[
https://issues.apache.org/jira/browse/RANGER-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4549:
---
Assignee: Pradeep Agrawal
> Non admin users cannot access /public/v2/api/roles/names and
> /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
> ---
>
> Key: RANGER-4549
> URL: https://issues.apache.org/jira/browse/RANGER-4549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Non admin users cannot access /public/v2/api/roles/names API, but can access
> the /public/v2/api/roles API and fetch the details of all the roles.
> Since the users can fetch the details from the roles API itself, the
> restriction for non admin users to access /roles/names and
> /roles/name/\{name} API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4551) No response returned for /assets/policyList/{service_name} API
[
https://issues.apache.org/jira/browse/RANGER-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4551:
---
Assignee: Pradeep Agrawal
> No response returned for /assets/policyList/{service_name} API
> --
>
> Key: RANGER-4551
> URL: https://issues.apache.org/jira/browse/RANGER-4551
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the /assets/policyList/\{service_name} API,
> the response is empty and the status code is 304 Not Modified.
> If there is no expected response, then the API has to be deprecated,
> otherwise the API has to be fixed to return the proper response
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4548) Return proper error message in the response for /tags/tags, /tags/resources and /tags/types API for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4548:
---
Assignee: Pradeep Agrawal
> Return proper error message in the response for /tags/tags, /tags/resources
> and /tags/types API for non admin users
> ---
>
> Key: RANGER-4548
> URL: https://issues.apache.org/jira/browse/RANGER-4548
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> /tags/tags and /tags/types, /tags/resources APIs are not accessible by non
> admin users,
> but when the users make a request, a proper error message should be returned
> stating that the users do not have privilege.
> Currently, the error message returned is not explanatory.
> Response returned for non admin users :-
> {code:java}
>
> content="IE=edge,chrome=1"> Ranger - Sign In name="description" content=""> content="width=device-width"> href="images/favicon.ico"> media="all" rel="stylesheet" type="text/css" id="bootstrap-css"> rel="stylesheet" href="styles/font-awesome.min.css"> href="styles/xa.css" media="all" rel="stylesheet" type="text/css"> src="libs/bower/jquery/js/jquery-3.5.1.js"> src="scripts/prelogin/XAPrelogin.js"> type="text/javascript">$(document).ready(function() {
> var updateBoxPosition = function() {
> $('#signin-container').css({'margin-top' :
> ($(window).height() - $('#signin-container').height()) / 2
> });};$(window).resize(updateBoxPosition);
>var queryParams = JSON.parse('{"' +
> decodeURI((location.href.split('?')[1] || 'g=0').replace(/=/g, "\":\"")) +
> '"}');if(queryParams.sessionTimeout){
> window.alert('Session Timeout');
> location.replace("login.jsp");}
> setTimeout(updateBoxPosition, 50);});
>
> id="signin-container" style="margin-top: 4.5px;">
>
>
>
> Username:
>
> Password:
> tabindex="2" autocomplete="off">
> style="color:white;display:none;">
>
> id="errorBoxUnsynced" class="help-inline"
> style="color:white;display:none;">User is not available in HDP Admin Tool.
> Please contact your Administrator.
> Sign In
>style="display: none;">
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4552) Response metrics for /assets/report is not proper, and pagination does not work
[
https://issues.apache.org/jira/browse/RANGER-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4552:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /assets/report is not proper, and pagination does not
> work
> ---
>
> Key: RANGER-4552
> URL: https://issues.apache.org/jira/browse/RANGER-4552
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the /assets/report API endpoint, the response
> metrics like
> result size is incorrect. Ideally, it should reflect the total number of
> objects returned
> {code:java}
> {"startIndex": 2,"pageSize": 100,"totalCount": 178,
> "resultSize": 0,"queryTimeMS": 1700217495822 {code}
> Even the pagination for the API does not work properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4545) DELETE /assets/resources/{resource_id} API should return proper status code for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4545:
---
Assignee: Pradeep Agrawal
> DELETE /assets/resources/{resource_id} API should return proper status code
> for non admin users
> ---
>
> Key: RANGER-4545
> URL: https://issues.apache.org/jira/browse/RANGER-4545
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a non admin user makes a DELETE request to
> /assets/resources/\{resource_id} endpoint, 405 method not allowed response is
> returned.
> The error message also contains HTML response.
> {code:java}
>
> HTTP Status 405 ? Method Not Allowed type="text/css">body {font-family: Tahoma, Arial,
> sans-serif;}
> h1,h2,h3,b {color: white;
>background-color: #525D76;}
> h1 {font-size: 22px;}
> h2 {font-size: 16px;}
> h3 {font-size: 14px;}
> p {font-size: 12px;}
> a {color: black;}
> .line {height: 1px;background-color: #525D76;
>border: none;}
> HTTP Status 405 ? Method Not Allowed
> {code}
> The status code / error message is not explanatory as ideally, a 403
> Forbidden or a 400 Bad Request status code with appropriate error message
> should be returned as the error should be related to the user permission.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4546) /assets/ugsyncAudits/{sync_source} API is accessible by user without permission on audit module
[
https://issues.apache.org/jira/browse/RANGER-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4546:
---
Assignee: Pradeep Agrawal
> /assets/ugsyncAudits/{sync_source} API is accessible by user without
> permission on audit module
> ---
>
> Key: RANGER-4546
> URL: https://issues.apache.org/jira/browse/RANGER-4546
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> A user without permission on the audits module is able to access the
> /assets/ugsyncAudits/\{sync_source} API.
> Ideally, the user should not be allowed to access the API, and it should
> result in a 403 error.
> If the same user tries to access the /assets/ugsyncAudits API, it results in
> a 403 error (as expected).
> Similarly, the behaviour has to be changed for the
> /assets/ugsyncAudits/\{sync_source} API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4562:
---
Assignee: Pradeep Agrawal
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74756: RANGER-4559: Migrate Ranger modules to junit5 - phase 1
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74756/#review226006 --- Ship it! Ship It! - Mehul Parikh On Nov. 25, 2023, 6:51 p.m., Kishor Gollapalliwar wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74756/ > --- > > (Updated Nov. 25, 2023, 6:51 p.m.) > > > Review request for ranger, Dineshkumar Yadav, Abhay Kulkarni, Madhan > Neethiraj, Mahesh Bandal, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja > Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-4559 > https://issues.apache.org/jira/browse/RANGER-4559 > > > Repository: ranger > > > Description > --- > > This sub-task is responsible to migrate following maven sub-modules to junit5. > > 01. conditions-enrichers > 02. credentialsbuilder > 03. embeddedwebserver > 04. jisql > 05. ldapconfigcheck > 06. ranger-atlas-plugin > 07. ranger-atlas-plugin-shim > 08. ranger-authn > 09. ranger-common-ha > 10. ranger-elasticsearch-plugin > 11. ranger-elasticsearch-plugin-shim > 12. ranger-hive-plugin > 13. ranger-hive-plugin-shim > 14. ranger-intg > 15. ranger-kafka-plugin > 16. ranger-kafka-plugin-shim > > > Diffs > - > > credentialbuilder/pom.xml c18d5585c > > credentialbuilder/src/test/java/org/apache/ranger/credentialapi/TestCredentialReader.java > ff3ce843e > > credentialbuilder/src/test/java/org/apache/ranger/credentialapi/Testbuildks.java > c9fb54c00 > hive-agent/pom.xml 8a21ab81d > > hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java > 2f6f1d846 > > hive-agent/src/test/java/org/apache/ranger/services/hive/TestAllHiveOperationInRanger.java > d424bb4fb > intg/pom.xml 4654ef7f7 > intg/src/test/java/org/apache/ranger/TestRangerClient.java 7da6b18a5 > plugin-kafka/pom.xml 9fa913741 > > plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerGSSTest.java > f33405a2f > > plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerSASLSSLTest.java > 90bd628f8 > > plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerAuthorizerTest.java > 9a7d5fe83 > > plugin-kafka/src/test/java/org/apache/ranger/authorization/kafka/authorizer/KafkaRangerTopicCreationTest.java > e48dd2535 > ranger-authn/pom.xml 4ee98f8a5 > ranger-common-ha/pom.xml 2faa243e4 > > ranger-common-ha/src/test/java/org/apache/ranger/ha/service/TestRangerServiceServerIdSelector.java > 0cd55a2a6 > ranger-examples/conditions-enrichers/pom.xml 70e9c6c74 > > ranger-examples/conditions-enrichers/src/test/java/org/apache/ranger/plugin/conditionevaluator/RangerSampleSimpleMatcherTest.java > 22e298df5 > > > Diff: https://reviews.apache.org/r/74756/diff/1/ > > > Testing > --- > > 1. mvn clean compile package install > 2. mvn clean compile package install -Psecurity-admin-react > > > Thanks, > > Kishor Gollapalliwar > >
[jira] [Assigned] (RANGER-4555) Response metrics for /assets/assets API not proper
[
https://issues.apache.org/jira/browse/RANGER-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran reassigned RANGER-4555:
Assignee: Ramachandran
> Response metrics for /assets/assets API not proper
> --
>
> Key: RANGER-4555
> URL: https://issues.apache.org/jira/browse/RANGER-4555
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Ramachandran
>Priority: Major
>
> When a request is made to /assets/assets API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of assets (the
> value returned by /assets/assets/count API is proper).
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4552) Response metrics for /assets/report is not proper, and pagination does not work
[
https://issues.apache.org/jira/browse/RANGER-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran reassigned RANGER-4552:
Assignee: Ramachandran
> Response metrics for /assets/report is not proper, and pagination does not
> work
> ---
>
> Key: RANGER-4552
> URL: https://issues.apache.org/jira/browse/RANGER-4552
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Ramachandran
>Priority: Major
>
> When a request is made to the /assets/report API endpoint, the response
> metrics like
> result size is incorrect. Ideally, it should reflect the total number of
> objects returned
> {code:java}
> {"startIndex": 2,"pageSize": 100,"totalCount": 178,
> "resultSize": 0,"queryTimeMS": 1700217495822 {code}
> Even the pagination for the API does not work properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4554) Response metrics for /assets/resources not proper
[
https://issues.apache.org/jira/browse/RANGER-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran reassigned RANGER-4554:
Assignee: Ramachandran
> Response metrics for /assets/resources not proper
> -
>
> Key: RANGER-4554
> URL: https://issues.apache.org/jira/browse/RANGER-4554
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Ramachandran
>Priority: Major
>
> When a request is made to /assets/resources API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of resources
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4553) Response metrics for /xaudit/trx_log not proper
[
https://issues.apache.org/jira/browse/RANGER-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran reassigned RANGER-4553:
Assignee: Ramachandran
> Response metrics for /xaudit/trx_log not proper
> ---
>
> Key: RANGER-4553
> URL: https://issues.apache.org/jira/browse/RANGER-4553
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Ramachandran
>Priority: Major
>
> When a request is made to /xaudit/trx_log API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 200,"totalCount": 0,
> "resultSize": 0,"queryTimeMS": 1700214070565, ...} {code}
> Ideally, the total count value should reflect the total number of logs
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
