ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Babiichuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-9797) Retry functionality does not work on Kerberize cluster page.
Date Wed, 25 Feb 2015 16:37:05 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrii Babiichuk updated AMBARI-9797:
-------------------------------------
    Attachment: AMBARI-9797_branch_2.0.patch
                AMBARI-9797.patch

> Retry functionality does not work on Kerberize cluster page.
> ------------------------------------------------------------
>
>                 Key: AMBARI-9797
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9797
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9797.patch, AMBARI-9797_branch_2.0.patch
>
>
> STR:
> Deploy a cluster from kerb-dev branch
> Go to kerberize cluster page
> Make the ongoing request for kerberizing cluster page fail. (Note: As of now it is failing
by default. Screenshot attached)
> On failure, retry link is shown on UI. Request triggered via retry link does not return
request ID or create any tasks.
> This happens because the security_state of the host components are marked as 'SECURED_KERBEROS'
even though cluster kerberizing request has the corresponding task failures



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

Mime
View raw message