ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-22108) Dismissing Enable Kerberos wizard initiates Disable kerberos call
Date Mon, 02 Oct 2017 14:19:00 GMT


Hadoop QA commented on AMBARI-22108:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Dismissing Enable Kerberos wizard initiates Disable kerberos call
> -----------------------------------------------------------------
>                 Key: AMBARI-22108
>                 URL:
>             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
> *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

View raw message