[
https://issues.apache.org/jira/browse/AMBARI-13504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967501#comment-14967501
]
Hadoop QA commented on AMBARI-13504:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12767795/AMBARI-13504.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4023//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4023//console
This message is automatically generated.
> Enable Ranger plugin properties should be validated to have same value as in
> Ranger service
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-13504
> URL: https://issues.apache.org/jira/browse/AMBARI-13504
> Project: Ambari
> Issue Type: Task
> Components: stacks
> Affects Versions: 2.1.3
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13504.patch
>
>
> This is to detect deviations in Ranger plugin properties for individual
> services from the central plugin config in Ranger service.
> ||Base property||Derived property||stack||
> |ranger-env/ranger-hdfs-plugin-enabled|ranger-hdfs-plugin-properties/ranger-hdfs-plugin-enabled|HDP-2.2
> onwards|
> |ranger-env/ranger-hive-plugin-enabled|ranger-hive-plugin-properties/ranger-hive-plugin-enabled|HDP-2.2
> onwards|
> |ranger-env/ranger-hbase-plugin-enabled|ranger-hbase-plugin-properties/ranger-hbase-plugin-enabled|HDP-2.2
> onwards|
> |ranger-env/ranger-knox-plugin-enabled|ranger-knox-plugin-properties/ranger-knox-plugin-enabled|HDP-2.2
> onwards|
> |ranger-env/ranger-kafka-plugin-enabled|ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled|HDP-2.3
> onwards|
> |ranger-env/ranger-yarn-plugin-enabled|ranger-yarn-plugin-properties/ranger-yarn-plugin-enabled|HDP-2.3
> onwards|
> |ranger-env/ranger-storm-plugin-enabled|ranger-storm-plugin-properties/ranger-storm-plugin-enabled|HDP-2.2
> onwards|
> This translates to following behavior on web-ui:
> If value of ranger-env/ranger-hdfs-plugin-enabled is false on Ranger smart
> config page and user changes the value of
> ranger-hdfs-plugin-properties/ranger-hdfs-plugin-enabled to true on HDFS
> service page and saves the configuration then it should show validation error
> saying that the value of ranger-env/ranger-hdfs-plugin-enabled and
> ranger-hdfs-plugin-properties/ranger-hdfs-plugin-enabled should always be same
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
