ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Babiichuk (JIRA)" <>
Subject [jira] [Commented] (AMBARI-9356) Handle the scenario where the Kerb API call returns 200
Date Tue, 27 Jan 2015 15:54:34 GMT


Andrii Babiichuk commented on AMBARI-9356:

+1 for the patch

> Handle the scenario where the Kerb API call returns 200
> -------------------------------------------------------
>                 Key: AMBARI-9356
>                 URL:
>             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|;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|;a=blob;f=ambari-web/app/messages.js;h=cb67812fb6c5e4371bb417ac0a1d358d83a228c5;hb=HEAD#l1010])
and enable next button

This message was sent by Atlassian JIRA

View raw message