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

Hadoop QA commented on AMBARI-11136:
------------------------------------

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

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

This message is automatically generated.

> Add host kerberos client install does not have command text
> -----------------------------------------------------------
>
>                 Key: AMBARI-11136
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11136
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11136_01.patch, add-host-kerb.png, 
> add_service_log.png, background_operations_log.png
>
>
> Kerb cluster, add host.
> See screen shot
> This issue appears to be a front end issue.  Here is the culprit: 
> {code:title=app/templates/wizard/step9/step9HostTasksLogPopup.hbs:47}
> {{taskInfo.role}} {{taskInfo.command}}
> {code}
> Rather then attempting to use the task's _command_detail_ value, the front 
> end only displays the task's _role_ and _command_ values which are 
> constrained by the code to be a certain set of values. The _command_detail_ 
> field does not have that constraint.  
> For the offending items in the relevant view,  the following values are set:
> {code}
> role: KERBEROS_CLIENT (translated somewhere to "Kerberos Client")
> command: CUSTOM_COMMAND (translated somewhere to "custom command")
> command_details: SET_KEYTAB KERBEROS/KERBEROS_CLIENT
> {code}
> On this note there are several items in that same display (for the Ambari 
> server host) that read "Ambari Server Action execute". This is the same issue.
> !add_service_log.png!
> The background operations view displays these values properly:
> !background_operations_log.png!



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

Reply via email to