Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 23 Aug 2017 20:05:02 +0000 (UTC)
From: "Robert Levas (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13097125.1503517917000.104836.1503518702197@Atlassian.JIRA>
In-Reply-To: <JIRA.13097125.1503517917000@Atlassian.JIRA>
References: <JIRA.13097125.1503517917000@Atlassian.JIRA> <JIRA.13097125.1503517917564@jira-lw-us.apache.org>
Subject: [jira] [Updated] (AMBARI-21798) Oozie server crashes post migration
 after regen kerberos keytabs and restart all services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 23 Aug 2017 20:05:09 -0000


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

Robert Levas updated AMBARI-21798:
----------------------------------
    Description: 
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)

  was:
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

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

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)


> 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
>
>
> 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)