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

Hadoop QA commented on AMBARI-21798:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12883467/AMBARI-21798_branch-2.5_01.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12056//console

This message is automatically generated.

> Oozie server crashes post migration after regen kerberos keytabs and restart 
> all services
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21798
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21798
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.2
>            Reporter: Di Li
>            Assignee: Robert Levas
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21798_branch-2.5_01.patch, 
> AMBARI-21798_branch-2.6_01.patch, AMBARI-21798_trunk_01.patch
>
>
> This is specifically for the IOP *4.2.0 *to HDP migration
> Start with an IOP 4.2.0 cluster with both Oozie and Knox installed, enable 
> Kerberos then run thru the migration. Once EU is finalized, regen Kerberos 
> keytabs via Ambari web UI and check the checkbox to make Ambari restart all 
> services as part of the regen process.
> Notice Oozie crashes after a successful restart with following error in the 
> oozie.log file
> {noformat}
> 2017-08-23 12:39:48,480 FATAL Services:514 - SERVER[umiak2.fyre.ibm.com] 
> E0550: Could not normalize host name [${host}], Could not resolve host 
> [${host}], ${host}: Name or service not known 
> org.apache.oozie.service.ServiceException: E0550: Could not normalize host 
> name [${host}], Could not resolve host [${host}], ${host}: Name or service 
> not known
> {noformat}
> This is because Knox kerberos.json in IOP 4.2.0 has oozie proxy setting as 
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts": "$\{hosts\}",}}
> In HDP 2.6.2, the same property  is now 
> {{"oozie.service.ProxyUserService.proxyuser.$\{knox-env/knox_user\}.hosts": 
> "$\{clusterHostInfo/knox_gateway_hosts\}"}}, where the $\{hosts\} placeholder 
> is changed and Knox params.py no longer has the logic to calculate it .
> *A manual fix* is to change Kerboers config for Knox - update 
> {{"oozie.service.ProxyUserService.proxyuser.knox.hosts"}} to have value 
> {{"$\{clusterHostInfo/knox_gateway_hosts\}"}}  ( done via UI, this will kick 
> off regen keytabs and restart services)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to