[
https://issues.apache.org/jira/browse/AMBARI-19585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826860#comment-15826860
]
Hadoop QA commented on AMBARI-19585:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847808/AMBARI-19585.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10105//console
This message is automatically generated.
> 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
>
> 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)
