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

Hudson commented on AMBARI-8387:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit-docker #276 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/276/])
AMBARI-8387. Alerts UI: Create definition details for 5 types of definitions. 
(akovalenko) (akovalenko: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=92f794eb3c8bf19c915797fc0bb983b6c0de8474)
* ambari-web/app/mappers/stack_service_mapper.js
* ambari-web/test/models/stack_service_test.js
* ambari-web/app/routes/installer.js
* ambari-web/app/routes/add_service_routes.js
* ambari-web/app/models/stack_service.js
* ambari-web/test/views/common/custom_date_popup_test.js


> Kerberos service should not be shown on Select Services page in Installer or 
> Add Service wizard
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8387
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8387
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8387.patch
>
>
> After [AMBARI-7448 | https://issues.apache.org/jira/browse/AMBARI-7448] 
> commit, HDP-2.2 stack has kerberos as a service. But this service is not 
> meant to be shown for selection on Installer or Add Service wizard. We will 
> have a seperate wizard for enabling Kerberos service in the cluster.
> There is a bug filed for getting such information from stacks API but doesn't 
> looks like this will be addressed sooner. 
> For now, we will have to implement this in the UI by hardcoding Kerberos 
> service reference in the UI code (stackService model or Select services page)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to