[
https://issues.apache.org/jira/browse/AMBARI-16767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-16767:
-----------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2.4.0
> 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)
