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

Hudson commented on AMBARI-9627:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #1764 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1764/])
AMBARI-9627. RU - NodeManager failed to restart in Kerberized clusters 
(alejandro) (afernandez: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=19ff44731b983f3251211411cb4678e987e445f2)
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params.py


> RU - NodeManager failed to restart in Kerberized clusters
> ---------------------------------------------------------
>
>                 Key: AMBARI-9627
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9627
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9627.patch
>
>
> Node Manager failed to restart in a Kerberized cluster while performing a 
> Rolling Upgrade.
> I deployed a 3-node cluster with all services from HDDFS through ZK, then 
> enabled Namenode HA, and kerberized the cluster.
> When I performed a RU from 2.2.0.0 GA bits to 2.2.1.0-2260, I first had to 
> comment out an error in ZK server, and when I got to the Slaves group, 
> NodeManager failed. See attached log.
> {code}
> Fail: Execution of '/usr/bin/kinit -kt 
> /etc/security/keytabs/nm.service.keytab nm/[email protected];' returned 1. 
> kinit: Keytab contains no suitable keys for nm/[email protected] while 
> getting initial credentials
> {code}
> {code}
> [root@c6404 ~]# klist -kt /etc/security/keytabs/nm.service.keytab
> Keytab name: FILE:/etc/security/keytabs/nm.service.keytab
> KVNO Timestamp         Principal
> ---- ----------------- 
> --------------------------------------------------------
>    1 02/12/15 23:23:29 nm/[email protected]
>    1 02/12/15 23:23:29 nm/[email protected]
>    1 02/12/15 23:23:29 nm/[email protected]
>    1 02/12/15 23:23:29 nm/[email protected]
>    1 02/12/15 23:23:29 nm/[email protected]
> {code}
> This means that params.py is probably missing to replace _HOST with the value.



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

Reply via email to