You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Oleg Nechiporenko (JIRA)" <ji...@apache.org> on 2016/05/19 12:27:12 UTC

[jira] [Commented] (AMBARI-16767) Persist UI console errors

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

Oleg Nechiporenko commented on AMBARI-16767:
--------------------------------------------

+1 for patch

> 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)