[jira] [Commented] (AMBARI-10452) Ambari unable to start services using non-default kinit_path_local

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

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

Hadoop QA commented on AMBARI-10452:
------------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified test files.

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

This message is automatically generated.

> Ambari unable to start services using non-default kinit_path_local
> ------------------------------------------------------------------
>
>                 Key: AMBARI-10452
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10452
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos
>             Fix For: 2.1.0, 2.0.1
>
>         Attachments: AMBARI-10452_trunk_01.patch, AMBARI-10452_trunk_02.patch
>
>
> PROBLEM: Ambari is unable to start services after running the Enable Security wizard on a cluster that uses a non-standard path to the Kerberos utilities, such as kinit.
> STEPS TO REPRODUCE: 
> 1. Start with non-Kerberized cluster (2.2 Sandbox works fine)
> 2. Move Kerberos utilities from /usr/bin/ to a new location, example: /usr/myorg/bin/
> 3. Run 'Enable Security' wizard in Ambari, specify new path for kinit, Apply
> 4. Watch 'Start All Services' step fail
> 5. Attempt to 'Restart all components with Stale Configs for HDFS,' which fails with the following error:
> Fail: Execution of ' -kt /etc/security/keytabs/hdfs.headless.keytab hdfs' returned 127. -bash: -kt: command not found
> Due to the error that occurs with trying to manually restart the HDFS service, it seems like kinit_path_local is empty when the path to kinit is modified. It looks like each service uses the function from:
> ./ambari-common/src/main/python/resource_management/libraries/functions/get_kinit_path.py
> But typically only these three hardcoded paths are passed to that function:
> /usr/bin, /usr/kerberos/bin, /usr/sbin
> The custom path defined in Ambari is never passed to that function, so the result is always empty.



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