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

Hadoop QA commented on AMBARI-8387:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12682456/AMBARI-8387.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 .

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/695//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/695//console

This message is automatically generated.

> 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