[
https://issues.apache.org/jira/browse/AMBARI-19585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828368#comment-15828368
]
Hudson commented on AMBARI-19585:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #752 (See
[https://builds.apache.org/job/Ambari-branch-2.5/752/])
AMBARI-19585. Client config tags may not be saved by agent (Attila (smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8635714c159803383ddc3559542b3445f4608212])
* (edit) ambari-agent/src/main/python/ambari_agent/Controller.py
* (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
* (edit) ambari-agent/src/test/python/ambari_agent/TestController.py
> Client config tags may not be saved by agent
> --------------------------------------------
>
> Key: AMBARI-19585
> URL: https://issues.apache.org/jira/browse/AMBARI-19585
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.5.0
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19585.patch
>
>
> Ambari agent does not save the config tags (eg. "V1") during component
> installation if it cannot determine that the component is a client. For this
> decision it requests the list of services/components right after it receives
> the first status command, which might happen after some client components are
> already installed. If the initial tags are missing, no subsequent config
> changes trigger updates on the affected host (except forced update via
> "Service Actions > Refresh configs").
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
