incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-3314) Loading of Monitoring UI gets stuck
Date Tue, 24 Sep 2013 00:45:02 GMT

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

Jaimin D Jetly commented on AMBARI-3314:
----------------------------------------

This issue is produced due to AMBARI-3315. A variable that was set after an API call (made
async in the patch) was accessed before being populated. This resulted in js error. As a fix
for AMBARI-3315, we no longer call API on step2 and step3 of security wizard but store user
information in localdb on Admin->security page. Thereafter in step2 and step3, we access
the information from localdb. Thus we don't need to make this API call as blocking call.
                
> Loading of Monitoring UI gets stuck
> -----------------------------------
>
>                 Key: AMBARI-3314
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3314
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.1
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3314.patch
>
>
> To reproduce follow these steps:
> (Stack 2.0.5)
> 1. Go to Admin page;
> 2. Select "Security" tab and click on "Enable Security" button.
> 3. Go to "Create Principals and Keytabs" tab.
> 4. Refresh page and wait some time.
> 5. Close wizard window.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message