[
https://issues.apache.org/jira/browse/AMBARI-22654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maciej Sitarz updated AMBARI-22654:
-----------------------------------
Attachment: host5_slave_client.png
host4_client.png
host3_slave.png
host2_master.png
host1_master.png
all_hosts.png
Screen captures of the "Install, Start and Test" step from "Add Service Wizard"
> Kerberos: Kerberos-related tasks occur after INSTALL stage of services being
> added
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-22654
> URL: https://issues.apache.org/jira/browse/AMBARI-22654
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.3, 2.5.2
> Reporter: Maciej Sitarz
> Assignee: Robert Levas
> Priority: Critical
> Attachments: SAMPLESRV2_v1.tgz, all_hosts.png, host1_master.png,
> host2_master.png, host3_slave.png, host4_client.png, host5_slave_client.png
>
>
> Kerberos-related configs (keytab,principal creation) are not applied before
> INSTALL command is built on add service.
> This occurs when new services and components are added to an existing cluster
> where Kerberos is enabled. Due to the order Kerberos-related configurations
> (keytabs, principals) will not be available for new services INSTALL step
> functions.
> This seems to be identical problem to the one mentioned in #AMBARI-17772
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
