[
https://issues.apache.org/jira/browse/AMBARI-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336942#comment-14336942
]
Hadoop QA commented on AMBARI-9797:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700793/AMBARI-9797_branch_2.0.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/1814//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1814//console
This message is automatically generated.
> 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)
