You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/11/20 12:04:10 UTC
[jira] [Commented] (AMBARI-13985) alerts should log into
ambari-agent.log rather than to ambari-agent.out
[ https://issues.apache.org/jira/browse/AMBARI-13985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015605#comment-15015605 ]
Hudson commented on AMBARI-13985:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #902 (See [https://builds.apache.org/job/Ambari-branch-2.1/902/])
AMBARI-13985. alerts should log into ambari-agent.log rather than to (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b1dd0f22451690a6b7db7003b5684685d0703cda])
* ambari-agent/src/main/python/ambari_agent/alerts/script_alert.py
* ambari-common/src/main/python/resource_management/core/environment.py
> alerts should log into ambari-agent.log rather than to ambari-agent.out
> -----------------------------------------------------------------------
>
> Key: AMBARI-13985
> URL: https://issues.apache.org/jira/browse/AMBARI-13985
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Port changes from AMBARI-13310 into `branch-2.1`.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)