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

Hadoop QA commented on AMBARI-8328:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12681472/AMBARI-8328.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/643//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/643//console

This message is automatically generated.

> Storm service check fails if the keytab generation is done via wizard CSV file
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-8328
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8328
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>         Environment: specific to HDP-2.2 stack
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>            Priority: Blocker
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-8328.patch, AMBARI-8328_branch-1.7.0.patch
>
>
> CSV file does not have an entry for storm principal and keytab for Storm UI 
> Server host. This eventually leads to storm service check failure due to 
> unavailability of storm principal by storm ui server.
> Note: This issue will not be hit if storm ui server is cohosted with other 
> storm service component (Supervisor or Nimbus).



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

Reply via email to