[
https://issues.apache.org/jira/browse/AMBARI-17266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333038#comment-15333038
]
Hadoop QA commented on AMBARI-17266:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12810970/AMBARI-17266.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7369//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7369//console
This message is automatically generated.
> StackDeploys: Suse: after enabling ranger plugin save button is always present
> ------------------------------------------------------------------------------
>
> Key: AMBARI-17266
> URL: https://issues.apache.org/jira/browse/AMBARI-17266
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Richard Zang
> Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17266.patch
>
>
> 1. Deploy cluster using BP
> 2. enable ranger plugins
> 3. save configs
> Expected: Configs should be saved and save button should be disabled
> Actual: even after save and clicking Ok on confirmation "Save" button is
> enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
