ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17516) UI - Customize Atlas Service configs shows incorrect required properties and Next button after toggling type
Date Mon, 04 Jul 2016 18:29:10 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-17516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361688#comment-15361688
] 

Hudson commented on AMBARI-17516:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #5222 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5222/])
AMBARI-17516. UI - Customize Atlas Service configs shows incorrect (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=be9da0bff0372ce0a6acf3cc58c3b4a84be6558c])
* ambari-web/app/views/common/configs/widgets/config_widget_view.js
* ambari-web/app/models/configs/objects/service_config_property.js
* ambari-web/app/models/configs/objects/service_config.js
* ambari-web/test/models/configs/objects/service_config_test.js


> 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)

Mime
View raw message