You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/06/22 21:09:00 UTC

[jira] [Commented] (AMBARI-12065) Core-site config reverted after enabling NN HA

    [ https://issues.apache.org/jira/browse/AMBARI-12065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596467#comment-14596467 ] 

Hadoop QA commented on AMBARI-12065:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12741032/AMBARI-12065_01.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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/3225//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3225//console

This message is automatically generated.

> Core-site config reverted after enabling NN HA
> ----------------------------------------------
>
>                 Key: AMBARI-12065
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12065
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Emil Anca
>            Assignee: Emil Anca
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12065_01.patch
>
>
> Steps to reproduce:
> * Install cluster with no HA
> * Set the following core-site.xml properties and restart affected services.
> ||Property||Value||
> |hadoop.http.authentication.simple.anonymous.allowed|false|
> |hadoop.http.authentication.signature.secret.file|/etc/security/http_secret|
> |hadoop.http.authentication.type|kerberos|
> |hadoop.http.authentication.kerberos.keytab|/etc/security/keytabs/spnego.service.keytab|
> |hadoop.http.authentication.kerberos.principal|HTTP/_HOST@EXAMPLE.COM|
> |hadoop.http.filter.initializers|org.apache.hadoop.security.AuthenticationFilterInitializer|
> |hadoop.http.authentication.cookie.domain|hortonworks.local|
> * Tell Ambari to authenticate itself {{ambari-server setup-security}} Option 3
> * Validate that UI's require authentication
> * Enable NN HA
> * Try looking at core-site.xml for all configuration properties and you'll notice they've been reverted to defaults



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)