[jira] [Commented] (AMBARI-18891) Oozie config not shown as stale upon changing DefaultFS

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

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

Hadoop QA commented on AMBARI-18891:
------------------------------------

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

This message is automatically generated.

> Oozie config not shown as stale upon changing DefaultFS
> -------------------------------------------------------
>
>                 Key: AMBARI-18891
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18891
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sebastian Toader
>            Assignee: Sebastian Toader
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18891.v1.patch
>
>
> Since Oozie has a dependency on configuration settings defined in core-site this has to be added to the it's dependencies list in the stack definition.
> Without this if a configuration setting is changed in core-site Oozie won't be flagged as having stale configs by Ambari thus the user won't know that Oozie service has to be restarted to pick up changes from the modified core-site.xml



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