[
https://issues.apache.org/jira/browse/AMBARI-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387698#comment-14387698
]
Hadoop QA commented on AMBARI-10285:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708256/AMBARI-10285.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/2187//console
This message is automatically generated.
> Storm Shows An Alert for REST_API Component After Stack Upgrade
> ---------------------------------------------------------------
>
> Key: AMBARI-10285
> URL: https://issues.apache.org/jira/browse/AMBARI-10285
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10285.patch
>
>
> # Upgraded cluster with storm.
> # Noticed a CRITICAL alert named "Storm REST API". But there are no REST API
> components on stack 2.2. The alert is linking to host with Storm UI Server.
> The underlying problem here is that, indeed, Storm REST API was removed on
> HDP 2.2. However, Ambari doesn't remove the relationships in the database; it
> just modifies the in-memory stack definitions.
> As a result, the alerts framework still thinks there's a REST_API component
> installed on a host. In order to preserve the historical entires for that
> component, alerts will determine at startup the definitions which may no
> longer be valid and will disable them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
