ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9356) Handle the scenario where the Kerb API call returns 200
Date Tue, 27 Jan 2015 16:06:35 GMT

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

Hadoop QA commented on AMBARI-9356:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12694794/AMBARI-9356.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/1505//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1505//console

This message is automatically generated.

> Handle the scenario where the Kerb API call returns 200
> -------------------------------------------------------
>
>                 Key: AMBARI-9356
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9356
>             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-9356.patch
>
>
> Generally a requestId is returned when cluster resource security_type field is updated.
This requestId is polled for showing task progress on Kerberos wizard's Kerberize cluster
page. ambari-web code takes care of this general scenario
> It is possible that the API call that updates security_type does not return anything
apart from calling success callback function when nothing needs to be done in the cluster
(existing cluster is already in kerberized state). This scenario should be gracefully handled
as part of this ticket.
> Link to the code ([link|https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=blob;f=ambari-web/app/mixins/wizard/wizardProgressPageController.js;h=9d12aff549205e61c19d5ec247e991eab96bcfc3;hb=HEAD#l64]).
The comment {{// step has been successfully completed}} needs to be followed by the code that
will show the existing success statement for this page ([link|https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=blob;f=ambari-web/app/messages.js;h=cb67812fb6c5e4371bb417ac0a1d358d83a228c5;hb=HEAD#l1010])
and enable next button



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message