[
https://issues.apache.org/jira/browse/AMBARI-14905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132958#comment-15132958
]
Hadoop QA commented on AMBARI-14905:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12786267/AMBARI-14905_trunk_02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5211//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5211//console
This message is automatically generated.
> Add API directive to force toggling Kerberos if the cluster's security type
> has not changed
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-14905
> URL: https://issues.apache.org/jira/browse/AMBARI-14905
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos, rest_api
> Fix For: 2.2.2
>
> Attachments: AMBARI-14905_branch-2.2_01.patch,
> AMBARI-14905_branch-2.2_02.patch, AMBARI-14905_branch-2.2_03.patch,
> AMBARI-14905_trunk_01.patch, AMBARI-14905_trunk_02.patch,
> AMBARI-14905_trunk_03.patch
>
>
> Add an API directive to force toggling Kerberos if the cluster's security
> type has not changed.
> This is useful for _retry_ attempts to enable or disable Kerberos when the
> workflow progressed far enough to store the _new_ security type.
> Trying to enable Kerberos when the cluster's security type is already set to
> {{KERBEROS}} will result in a successful response from the Ambari server but
> no actions will be performed. Same for attempting to disable Kerberos when
> the cluster's security type is already set to {{NONE}}.
> By forcing the operation using the {{force_toggle_kerberos=true}} directive,
> the security type check is avoided, thus allowing the _retry_ operation to
> proceed.
> Example:
> {code}
> PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
> {
> "Clusters" : {
> "security_type" : "KERBEROS"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
