You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/11/01 12:37:00 UTC
[jira] [Commented] (AMBARI-22341) A bunch of alerts fails due to
absence of configs
[ https://issues.apache.org/jira/browse/AMBARI-22341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234018#comment-16234018 ]
Hadoop QA commented on AMBARI-22341:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12895012/AMBARI-22341.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12592//console
This message is automatically generated.
> A bunch of alerts fails due to absence of configs
> -------------------------------------------------
>
> Key: AMBARI-22341
> URL: https://issues.apache.org/jira/browse/AMBARI-22341
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: AMBARI-22341.patch
>
>
> Previously we had a bug/hack where alerts used some configurations (like
> hostLevelParams,commandParams etc.) from the information saved by status
> commands.
> Now the achitecture changed, we don't have this hack in place anymore. This
> requires a non-hacky solution. Meaning alerts should be able to access
> configurations outside of 'configurations' dictionary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)