[jira] [Commented] (AMBARI-11027) Kerberos: cleanup Manual kerb req text

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-11027:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12731484/AMBARI-11027_01.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 .

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

This message is automatically generated.

> Kerberos: cleanup Manual kerb req text
> --------------------------------------
>
>                 Key: AMBARI-11027
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11027
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos, kerberos-wizard
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11027_01.patch
>
>
> Update checkbox "reqs" on Page 1 of wizard with choice of Manual Kerb:
> * Cluster hosts have network access to the KDC
> * Kerberos client utilities (such as kinit) have been installed on every cluster host
> * The Java Cryptography Extensions (JCE) have been setup on the Ambari Server host and all hosts in the cluster
> * The Service and Ambari Principals will be manually created in the KDC before completing this wizard
> * The keytabs for the Service and Ambari Principals will be manually created and distributed to cluster hosts before completing this wizard



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