[jira] [Commented] (AMBARI-10550) NameNode Restart fails after attempt to Kerberize Cluster

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-10550:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12726217/AMBARI-10550_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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2398//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2398//console

This message is automatically generated.

> NameNode Restart fails after attempt to Kerberize Cluster
> ---------------------------------------------------------
>
>                 Key: AMBARI-10550
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10550
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10550_01.patch
>
>
> When attempting to restart the HDFS NameNode after running the Kerberos wizard to enable Kerberos, the NameNode fails to startup.  
> The underlying failure in the ambari-agent appears to be:
> "Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", line 298, in <module>
>     NameNode().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 214, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", line 72, in start
>     namenode(action="start", rolling_restart=rolling_restart, env=env)
>   File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk
>     return fn(*args, **kwargs)
>   File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py", line 38, in namenode
>     setup_ranger_hdfs()
>   File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py", line 66, in setup_ranger_hdfs
>     hdfs_repo_data = hdfs_repo_properties()
>   File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py", line 194, in hdfs_repo_properties
>     config_dict['dfs.datanode.kerberos.principal'] = params._dn_principal_name
> AttributeError: 'module' object has no attribute '_dn_principal_name'"
> This keeps the HDFS NameNode from starting up properly after Kerberos is Enabled, and this seems to keep the process of Enabling Kerberos from completing.  
> The problem appears to be a Python coding issue where _private_ variables (declared with a leading underscore) are not imported from {{common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py}} into {{common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py}}.



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