[
https://issues.apache.org/jira/browse/AMBARI-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806661#comment-15806661
]
Hudson commented on AMBARI-19392:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6383 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6383/])
AMBARI-19392. Status command executor may use obsolete settings. (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e7c027c96d0c319552e68008304777e2642b3f7a])
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
* (edit) ambari-agent/src/main/python/ambari_agent/Controller.py
> Status command executor may use obsolete settings
> -------------------------------------------------
>
> Key: AMBARI-19392
> URL: https://issues.apache.org/jira/browse/AMBARI-19392
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 3.0.0
> Reporter: Doroszlai, Attila
> Assignee: Sebastian Toader
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19392.patch, AMBARI-19392.v2.patch
>
>
> Ambari agent launches status command executor in a subprocess (since
> AMBARI-18505), passing an instance of {{config}}. Afterwards the agent may
> receive settings from the server in the response to registration. These new
> config values are not visible in the subprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
