You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2017/10/02 12:11:01 UTC

[jira] [Updated] (AMBARI-22108) Dismissing Enable Kerberos wizard initiates Disable kerberos call

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

Andrii Tkach updated AMBARI-22108:
----------------------------------
    Attachment: Screen Shot 2017-09-29 at 3.07.59 PM.png

> 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: 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)