ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18657) Slider always creates storm slider conf directory
Date Fri, 21 Oct 2016 16:21:59 GMT


Hadoop QA commented on AMBARI-18657:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results:
Console output:

This message is automatically generated.

> Slider always creates storm slider conf directory
> -------------------------------------------------
>                 Key: AMBARI-18657
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk, 2.4.0, 2.5.0
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>            Priority: Minor
>             Fix For: trunk, 2.5.0, 2.4.2
>         Attachments: AMBARI-18657.patch
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> The script in common-services should respect all possible ways of installing
slider.  In a stack without storm there is no need to install the storm slider client RPM.
 As a result the storm slider client directory will be a broken link and attempting to create
the storm slider client config directory will result in an error.

This message was sent by Atlassian JIRA

View raw message