[
https://issues.apache.org/jira/browse/AMBARI-9335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292124#comment-14292124
]
Hadoop QA commented on AMBARI-9335:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12694576/AMBARI-9335.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1492//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1492//console
This message is automatically generated.
> Kerberos: Show progress spinner during Kerberize Cluster step in UI
> -------------------------------------------------------------------
>
> Key: AMBARI-9335
> URL: https://issues.apache.org/jira/browse/AMBARI-9335
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9335.patch
>
>
> I went to enable kerberos and after Configure Identities and Stop Services,
> the wizard performs a PUT and moves to the Kerberize Cluster step (create
> principals, create keytabs, etc)
> The UI hung since the PUT was taking a while (30+ seconds). On the wizard,
> you had the wizard shell, the title and a disabled next button. After some
> time, there was an error (backend) and an error dialog popped up.
> Minimum change is to have a spinner in the wizard area after the PUT to at
> least give the user a sense something is happening. Otherwise, looked like I
> was broken right away, vs. a PUT taking a really long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
