ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18891) Oozie config not shown as stale upon changing DefaultFS
Date Tue, 15 Nov 2016 13:58:58 GMT

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

Hudson commented on AMBARI-18891:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6015 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6015/])
AMBARI-18891. Oozie config not shown as stale upon changing DefaultFS. (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7df30b172d88271ffa5300149a73e86bf330a912])
* (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/metainfo.xml


> 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)

Mime
View raw message