[
https://issues.apache.org/jira/browse/AMBARI-16661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283087#comment-15283087
]
Hudson commented on AMBARI-16661:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4838 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4838/])
AMBARI-16661. Provide Information Message About Suspended Alerts During
(akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0b18f023b4188b952e3fc835da3f5a6ccf1e206e])
* ambari-web/app/messages.js
* ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs
> Provide Information Message About Suspended Alerts During Upgrade
> -----------------------------------------------------------------
>
> Key: AMBARI-16661
> URL: https://issues.apache.org/jira/browse/AMBARI-16661
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-16661.patch
>
>
> Ambari now suspends most outbound notifications during an HDP upgrade.
> Although the alerts will still show in the UI, the Ambari server will not
> dispatch alerts while:
> - An upgrade is in progress
> - An existing upgrade is suspended
> There are some alerts, however, which still remain active for triggering
> outbound notifications. These deal with mostly {{AMBARI/AMBARI_SERVER}} and
> {{AMBARI/AMBARI_AGENT}} alerts which are not associated with a cluster. For
> example:
> - Agent Disk Usage
> - Agent Heartbeats
> - Ambari Performance
> ... will all still produce notifications.
> The web client should provide an informational dialog that lets
> administrators know that outbound alerts, if configured, will be mostly
> suppressed during the upgrade. The web client can even see if there are any
> alert targets defined, and choose not to show the message if there are none
> configured.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
