You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/01/24 16:52:34 UTC

[jira] [Commented] (AMBARI-9317) Kerberos: Need stdout to show info on Kerberos-related tasks

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

Hadoop QA commented on AMBARI-9317:
-----------------------------------

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

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

This message is automatically generated.

> Kerberos: Need stdout to show info on Kerberos-related tasks
> ------------------------------------------------------------
>
>                 Key: AMBARI-9317
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9317
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9317_01.patch
>
>
> There's no stdout to indicate progress / success for the tasks for principal generation / keytab generation, etc.
> Also, even just to know what command is actually being run to create the principal, that will help folks with debugging. Or is that only shown in case of a failure. Just want to make sure in the case of a problem, there is output there to help folks.



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