[
https://issues.apache.org/jira/browse/AMBARI-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-7891:
-----------------------------------
Description:
# If cluster is kerberized, create krb5JAASLogin.conf file at /etc/knox/conf/
location. This file will be a template that fetches {{knox_gateway_principal}}
and {{knox_gateway_keytab}} values from knox-env file.
# Irrespective of cluster is kerberized or not, knox service check should be
executed by ambari smoke user. If cluster is kerberized then it should kinit
before executing the service check.
was:
# If cluster is kerberized, create krb5JAASLogin.conf file at /etc/knox/conf/
location. This file will be a template that fetches {{knox_gateway_principal}}
and {{knox_gateway_keytab}} values from knox-env file.
# Irrespective of cluster is kerberized or not, knox service check should be
executed by ambari smoke user. If cluster is kerberized then it should kinit
before executing the service check.
# If hiveserver2 config is changed to use http transport then Nagios should use
the http port to display alerts for HiveServer2 checks.
> Make changes in ambari-agent code to support knox kerberization
> ---------------------------------------------------------------
>
> Key: AMBARI-7891
> URL: https://issues.apache.org/jira/browse/AMBARI-7891
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-agent
> Affects Versions: 1.7.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Fix For: 1.7.0
>
>
> # If cluster is kerberized, create krb5JAASLogin.conf file at /etc/knox/conf/
> location. This file will be a template that fetches
> {{knox_gateway_principal}} and {{knox_gateway_keytab}} values from knox-env
> file.
> # Irrespective of cluster is kerberized or not, knox service check should be
> executed by ambari smoke user. If cluster is kerberized then it should kinit
> before executing the service check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
