[
https://issues.apache.org/jira/browse/AMBARI-22108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187992#comment-16187992
]
Hadoop QA commented on AMBARI-22108:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889951/AMBARI-22108_trunk.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12397//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12397//console
This message is automatically generated.
> Dismissing Enable Kerberos wizard initiates Disable kerberos call
> -----------------------------------------------------------------
>
> Key: AMBARI-22108
> URL: https://issues.apache.org/jira/browse/AMBARI-22108
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.2
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22108.patch, AMBARI-22108_trunk.patch, Screen
> Shot 2017-09-29 at 3.07.59 PM.png
>
>
> *STR:*
> # On last step (Start and Test services) of Enable Kerberos wizard dismiss
> the wizard
> *Expected behavior:* This should only dismiss the wizard and cluster should
> be kerberized successfully
> *Actual behavior:* UI makes disable kerberos API call when services are being
> started. This does server side operation for disable kerberos and marks
> kerberos security type as none. This puts cluster in inconsistent state with
> ambari showing cluster as non-kerberized and service configs having kerberos
> settings.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
