[jira] [Commented] (AMBARI-9849) .log Files are not placed in the changed directory in Ambari 1.6 and 1.7

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

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

Hadoop QA commented on AMBARI-9849:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12701608/AMBARI-9849.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:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> .log Files are not placed in the changed directory in Ambari 1.6 and 1.7
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-9849
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9849
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 1.6.1, 1.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9849.patch
>
>
> PROBLEM: When changing the location for storm log file (.log files) in Ambari 1.6/1.7, instead of it placing those files in the specified location, it places those files into the default location of /var/log/storm.
> BUSINESS IMPACT: This bug is preventing the customer from changing the location of their placement for their log files which is impacting their space for their filesystem as well as their business activities. Customer is expecting a quick turn-around on this issue.
> STEPS TO REPRODUCE: Support was able to reproduce this issue as well by going in to Ambari 1.6 and 1.7 to change the location for the storm log directories and these changes failed to go to the newly specified location. The .out files all went to the newly specified location.
> SUPPORT ANALYSIS: After seeing the defect it is obvious that this is a bug pertaining to the .log file directory change in Ambari 1.6 and 1.7 (both were tested).



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