[ 
https://issues.apache.org/jira/browse/TRAFODION-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liu ming reassigned TRAFODION-2935:
-----------------------------------

    Assignee: Eason Zhang  (was: Venkat Muthuswamy)

> Python installer does fails when Kerberos is enabled
> ----------------------------------------------------
>
>                 Key: TRAFODION-2935
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2935
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: Build Infrastructure
>    Affects Versions: 2.2-incubating
>            Reporter: Roberta Marton
>            Assignee: Eason Zhang
>            Priority: Major
>
> While testing the source tar for apache release 2.2, I was unable to complete 
> the installation.  the following error occurred:
> Host [rm1.novalocal]: Script [hdfs_cmds.py] 
> ..................................... [ FAIL ] 
> Failed to run command  su - hdfs -c '/usr/bin/hdfs dfs -chgrp 18/01/28 
> 21:15:25 WARN security.UserGroupInformation: PriviledgedActionException 
> as:root (auth:KERBEROS) cause:javax.security.sasl.SaslException: GSS initiate 
> failed [Caused by GSSException: No valid credentials provided (Mechanism 
> level: Failed to find any Kerberos tgt)]
> 18/01/28 21:15:25 WARN ipc.Client: Exception encountered while connecting to 
> the server : javax.security.sasl.SaslException: GSS initiate failed [Caused 
> by GSSException: No valid credentials provided (Mechanism level: Failed to 
> find any Kerberos tgt)
> There is a valid HBASE  ticket:
>  [centos@rm1 distribution]$ sudo su hdfs
> bash-4.1$ klist
> Ticket cache: FILE:/tmp/krb5cc_494
> Default principal: hdfs/rm1.novalo...@trafkdc.com
> Valid starting     Expires            Service principal
> 01/28/18 21:11:10  01/29/18 21:11:10  krbtgt/trafkdc....@trafkdc.com
>                 renew until 02/02/18 21:11:10
> I manually performed the hdfs_cmds.py step and completed the installation.  
> However, after installation completed, neither authorization or 
> authentication was enabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to