ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9627) RU - NodeManager failed to restart in Kerberized clusters
Date Fri, 13 Feb 2015 17:12:11 GMT

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

Hadoop QA commented on AMBARI-9627:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12698743/AMBARI-9627.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/1675//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1675//console

This message is automatically generated.

> 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/_HOST@EXAMPLE.COM;'
returned 1. kinit: Keytab contains no suitable keys for nm/_HOST@EXAMPLE.COM 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/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
> {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)

Mime
View raw message