You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Diego (JIRA)" <ji...@apache.org> on 2018/12/04 16:47:00 UTC
[jira] [Created] (AMBARI-24995) make dfs.permissions.superusergroup
as group property again
Diego created AMBARI-24995:
-------------------------------
Summary: make dfs.permissions.superusergroup as group property again
Key: AMBARI-24995
URL: https://issues.apache.org/jira/browse/AMBARI-24995
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Environment: ambari 2.7.1.0-169
HDP 3.0.1.0-187
CentOS 7.5
Reporter: Diego
Hi,
The [hdfs encryption guide|[https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.1/configuring-hdfs-encryption/content/create_an_hdfs_admin_user.html] []|https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.1/configuring-hdfs-encryption/content/create_an_hdfs_admin_user.html] for HDP 3.0.1 states "_In Ambari, replace the current value of dfs.permissions.superusergroup with the group name “operator”_" however, this option is not available from Ambari, so it looks like the fix applied in 2.6.0 ([AMBARI-22086|https://issues.apache.org/jira/browse/AMBARI-22086]) is not working for 2.7.1.
I also checked the workaround suggested in this [HW community post|[https://community.hortonworks.com/questions/155952/how-to-modify-dfspermissionssuperusergroup-in-hdp.html]] but commenting or even removing the tag does not change anything from Ambari's UI perspective.
Versions used:
ambari 2.7.1.0-169
HDP 3.0.1.0-187
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)