[
https://issues.apache.org/jira/browse/AMBARI-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320396#comment-14320396
]
Hudson commented on AMBARI-9615:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1762 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1762/])
AMBARI-9615 - Agents Do Not Update Cached Alert JSON On New Configurations
(jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=12ed8b5538faf0fd4093ddd68ceee26f39d486ec)
* ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py
* ambari-agent/src/main/python/ambari_agent/alerts/port_alert.py
*
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/alerts.json
* ambari-agent/src/test/python/ambari_agent/TestAlerts.py
* ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py
* ambari-agent/src/main/python/ambari_agent/Controller.py
* ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py
* ambari-agent/src/main/python/ambari_agent/alerts/script_alert.py
* ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py
> Agents Do Not Update Cached Alert JSON On New Configurations
> ------------------------------------------------------------
>
> Key: AMBARI-9615
> URL: https://issues.apache.org/jira/browse/AMBARI-9615
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-9615.patch
>
>
> When an execution command is sent to an agent, it only checks to see if any
> of the existing alerts have configuration data changes. If none do, the
> updated configurations are not written to definitions.json.
> On an execution command, definitions.json shoudl always have its
> configuration section updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
