ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8339) Alerts UI: Any changes to the alert definition are lost in next refresh
Date Sat, 15 Nov 2014 01:25:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14213242#comment-14213242
] 

Hudson commented on AMBARI-8339:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #953 (See [https://builds.apache.org/job/Ambari-trunk-Commit/953/])
AMBARI-8339. Alerts UI: Any changes to the alert definition are lost in next refresh.(xiwang)
(xiwang: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=816fe1f6c9995f0a970d41be5a1ee69fd049bb35)
* ambari-web/app/views/main/alerts/definition_details_view.js


> Alerts UI: Any changes to the alert definition are lost in next refresh
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-8339
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8339
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8339.patch
>
>
> When user goes to alert definition details page and clicks on any edit and hits save,
the changes hold only till the next refresh. Upon the next poll, the original values are shown.
I do not see any PUT calls for saving.
> We should make sure all changes are persisted via the API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message