[
https://issues.apache.org/jira/browse/AMBARI-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568087#comment-15568087
]
Joe Manning commented on AMBARI-11705:
--------------------------------------
We have experienced this issue with Ambari 2.4
# rpm -q ambari-server
ambari-server-2.4.1.0-22.x86_64
The issue occurs when we try to edit a notification for a service that is
stopped.
Or if one or more of the hosts running the service is not sending heartbeats to
the ambari-server.
To workaround the issue, we need restart the ambari server.
> Alerts Notifications: Groups and Severity cannot be edited
> ----------------------------------------------------------
>
> Key: AMBARI-11705
> URL: https://issues.apache.org/jira/browse/AMBARI-11705
> Project: Ambari
> Issue Type: Bug
> Components: alerts
> Affects Versions: 2.1.0
> Reporter: Chandana Mirashi
> Labels: Alerts-UI
> Attachments: AMBARI-11705.patch
>
>
> 1. During install create alert notification. Select group and severity.
> 2. Post install, edit alert notification. Make changes to Group and Severity
> then save.
> 3. Manage Alert Notifications text does not reflect the change.
> 4. Edit notification displays same information as before the change.
> 5. Close and reopen does not refresh information.
> Same case seen even after creating new notifications post
> install.Intermittently the clicking on save button does not close edit
> notification.
> One other scenario
> 1. Edit notification and change just the severity and save.
> 2. Manage Alert Notifications text does not reflect the change.
> 3. Close manage notification and open again. The page is refreshed and
> can see the changes made to Severity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
