[
https://issues.apache.org/jira/browse/AMBARI-15008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143213#comment-15143213
]
Hadoop QA commented on AMBARI-15008:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12787446/AMBARI-15008.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5318//console
This message is automatically generated.
> Use force_toggle_kerberos directive when retrying enable Kerberos on failure
> ----------------------------------------------------------------------------
>
> Key: AMBARI-15008
> URL: https://issues.apache.org/jira/browse/AMBARI-15008
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15008.patch
>
>
> Use {{force_toggle_kerberos directive}} when retrying enable Kerberos on
> failure rather than disabling and then re-enabling Kerberos.
> This occurs in the _Enable Kerberos Wizard_ if a failure occurs on the
> "Enable Kerberos" page and the _retry_ button_ is clicked.
> *Note*: to simulate an error condition on this step, stop the KDC (krb5kdc)
> and admin (kadmin) servers before transitioning to the "Enable Kerberos" page
> from the "Configure Identities" page in the "Enable Kerberos" wizard.
> To force a retry of enabling Kerberos, the following API call should be made:
> {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)
