[
https://issues.apache.org/jira/browse/AMBARI-22108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188223#comment-16188223
]
Hudson commented on AMBARI-22108:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #318 (See
[https://builds.apache.org/job/Ambari-branch-2.6/318/])
AMBARI-22108 Dismissing Enable Kerberos wizard initiates Disable (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4a29c923fdfd7d085e001704616e77acfdfecda1])
* (edit) ambari-web/app/routes/add_kerberos_routes.js
> 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)
