[
https://issues.apache.org/jira/browse/AMBARI-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666813#comment-15666813
]
Sebastian Toader commented on AMBARI-18891:
-------------------------------------------
The test that failed is unrelated to this change:
{code}
Failed tests:
FAIL: test_update_directory_archive
(TestResourceFilesKeeper.TestResourceFilesKeeper)
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/TestResourceFilesKeeper.py",
line 191, in test_update_directory_archive
self.assertTrue(write_hash_sum_mock.called)
AssertionError: False is not true
{code}
> 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)
