ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18474) Kerberos wizard loses request id on server restart
Date Tue, 27 Sep 2016 16:39:21 GMT


Hadoop QA commented on AMBARI-18474:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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
                        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 ambari-web.

Test results:
Console output:

This message is automatically generated.

> Kerberos wizard loses request id on server restart
> --------------------------------------------------
>                 Key: AMBARI-18474
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.2.2
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.5.0
>         Attachments: AMBARI-18474.patch, Screen Shot 2016-09-20 at 6.37.29 PM.png
> *Problem*
> - Kerberos wizard create principals action timed out
> - To increase task timeout we had to restart the server
> - On restart wizard comes up wit ha spinner, no error no indication of what is happening
> - had to post a last request id through js console for work to resume.
> - Quitting a wizard means users has to start from the very beginning, on a 1300 node
cluster that is not feasible.
> *Expected behavior*:
> - If the last request id was not perisisted by UI, on restart the last request id needs
to be retrieved and check for context info to resume from where the user left the wizard.

This message was sent by Atlassian JIRA

View raw message