You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2015/03/05 12:26:38 UTC
[jira] [Commented] (AMBARI-6652) amabri tries to create local
users/groups with a Kerberized cluster
[ https://issues.apache.org/jira/browse/AMBARI-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348626#comment-14348626 ]
Hari Sekhon commented on AMBARI-6652:
-------------------------------------
Checking back on this ticket after a couple months I see no movement and I'm also still having to work around this as an ongoing problem whenever adding nodes that are already LDAP+Kerberos integrated.
> 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
> Affects Versions: 1.6.0
> Reporter: Rémy SAISSY
> Priority: Blocker
>
> 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)