ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21798) Oozie server crashes post migration after regen kerberos keytabs and restart all services
Date Thu, 24 Aug 2017 13:58:00 GMT

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

Hudson commented on AMBARI-21798:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7930 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7930/])
AMBARI-21798. Oozie server crashes post migration after regen kerberos (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=60632536aa6fbcee96580c24d6e2d7f67dd184fa])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog252Test.java


> 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
>            Priority: Blocker
>             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)

Mime
View raw message