You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2015/02/25 17:40:04 UTC
[jira] [Commented] (AMBARI-9797) Retry functionality does not work
on Kerberize cluster page.
[ https://issues.apache.org/jira/browse/AMBARI-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336728#comment-14336728 ]
Aleksandr Kovalenko commented on AMBARI-9797:
---------------------------------------------
+1 for the 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)