[
https://issues.apache.org/jira/browse/AMBARI-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182183#comment-15182183
]
Bolke de Bruin commented on AMBARI-6652:
----------------------------------------
On the MISC tab while creating a cluster (step 7, Customize Services) you can
select "Skip group modifications during install". This actually disables user
and group creation entirely. It is not perfect (ie. no csv, but users are
listed).
I'm trying to figure out if it is possible to launch the creation of
centralized users earlier without too much hassle. At the moment it is assumed
user creation needs to be done on the cluster hosts and obviously when having
something like IPA the users need to exist before
> amabri tries to create local users/groups with a Kerberized cluster
> -------------------------------------------------------------------
>
> Key: AMBARI-6652
> URL: https://issues.apache.org/jira/browse/AMBARI-6652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.6.0, trunk, 2.2.0
> Reporter: Rémy SAISSY
> Priority: Blocker
> Labels: kerberos
>
> With a Kerberized cluster (using FreeIPA from CentOS 6.4 in my case), it is
> impossible to install/start services using Ambari.
> The cause is that Ambari (the
> hooks/before-INSTALL/scripts/shared_initialization.py::setup_users()) checks
> and creates users and groups as if there were no Kerberos.
> - check /etc/passwd and /etc/groups
> - use adduser, groupadd, usermod, groupmod
> It would be better to either :
> - add a dialog in Ambari to choose the CLI tools for dealing with
> users/groups check and creation
> - disable the check/creation and inform the end user of the users/groups
> that are required / generate a csv if needed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
