[
https://issues.apache.org/jira/browse/AMBARI-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361545#comment-15361545
]
Hadoop QA commented on AMBARI-17516:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816056/AMBARI-17516_updated.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 1 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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7683//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7683//console
This message is automatically generated.
> UI - Customize Atlas Service configs shows incorrect required properties and
> Next button after toggling type
> ------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-17516
> URL: https://issues.apache.org/jira/browse/AMBARI-17516
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17516.patch, AMBARI-17516_updated.patch
>
>
> STR:
> * Install Ambari 2.4
> * Install HDP 2.5 and attempt to install Atlas
> In the smart config section, notice that the default auth type is LDAP and
> that several properties are required, so the Next button is disabled. Then
> change the auth type to AD and notice that a different set of properties is
> required, however, the Next button is now enabled even though those configs
> don't have a value. That's a bug.
> If you then click proceed and then back button, and then change the auth type
> from AD to LDAP, it now shows the required properties for LDAP with "x"
> button but the Next button is still enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
