[
https://issues.apache.org/jira/browse/AMBARI-16767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291611#comment-15291611
]
Hudson commented on AMBARI-16767:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4878 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4878/])
AMBARI-16767. Persist UI console errors (alexantonenko) (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=234b9cdadadf9096ff49965b9c81b1abc3d5a751])
* ambari-web/app/controllers/global/errors_handler_controller.js
* ambari-web/app/controllers.js
> Persist UI console errors
> -------------------------
>
> Key: AMBARI-16767
> URL: https://issues.apache.org/jira/browse/AMBARI-16767
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16767.patch
>
>
> We have a lot of situations when after page refresh or re login issue/console
> error is gone and there is no opportunity to track and understand the root
> source of the problem. The easiest way is to at least persist this error. So
> for example after CI tests we can login to cluster that has an issue and see
> all UI errors that it had.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
