ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-10550) NameNode Restart fails after attempt to Kerberize Cluster
Date Sat, 18 Apr 2015 02:32:59 GMT

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

Hudson commented on AMBARI-10550:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2359 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2359/])
AMBARI-10550. NameNode Restart fails after attempt to Kerberize Cluster (rlevas) (rlevas:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7c3015fee5afd647c73b1af6ac492569dc958ee4)
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/setup_ranger_hdfs.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py


> 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)

Mime
View raw message