[
https://issues.apache.org/jira/browse/AMBARI-14026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-14026:
--------------------------------------
Description:
The Ambari server handling of proxyuser settings has been updated in the UI's
handling of cluster configuration to use the "*" setting for the default group.
Since the Blueprint configuration processor still handles configuration
separately in some respects, this default is now handled differently for the
most part in Blueprints, as the Blueprint processor will still set the default
to be "users".
For example, the Blueprint processor currently sets the Hive-specific proxyuser
group property to:
"hadoop.proxyuser.hive.groups" : "users",
The Blueprint processor should be updated, such that the default is now "*"
for this property, and for all other service-specific proxyuser.*.groups
properties in core-site.xml.
Since not all environments include the "users" group, the "*" group is a more
valid default value for this property. This change will also bring the
Blueprint processor more closely in-line with the behavior of the UI, and so
making the configuration more consistent across both options.
I'm working on a fix for this, and will be submitting a patch shortly.
was:
The Ambari server handling of proxyuser settings has been updated in the UI's
handling of cluster configuration to use the "*" setting for the default group.
Since the Blueprint configuration processor still handles configuration
separately in some respects, this default is now handled differently for the
most part in Blueprints, as the Blueprint processor will still set the default
to be "users".
For example, the Blueprint processor currently sets the Hive-specific proxyuser
group property to:
"hadoop.proxyuser.hive.groups" : "users",
The Blueprint processor should be updated, such that the default is now "*" for
this property, and for all other service-specific proxyuser.*.groups properties
in core-site.xml.
Since not all environments include the "users" group, the "*" group is a more
valid default value for this property. This change will also bring the
Blueprint processor more closely in-line with the behavior of the UI, and so
making the configuration more consistent across both options.
I'm working on a fix for this, and will be submitting a patch shortly.
> Blueprints not setting correct defaults for HDFS proxyuser group settings
> -------------------------------------------------------------------------
>
> Key: AMBARI-14026
> URL: https://issues.apache.org/jira/browse/AMBARI-14026
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.3
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The Ambari server handling of proxyuser settings has been updated in the UI's
> handling of cluster configuration to use the "*" setting for the default
> group.
> Since the Blueprint configuration processor still handles configuration
> separately in some respects, this default is now handled differently for the
> most part in Blueprints, as the Blueprint processor will still set the
> default to be "users".
> For example, the Blueprint processor currently sets the Hive-specific
> proxyuser group property to:
> "hadoop.proxyuser.hive.groups" : "users",
> The Blueprint processor should be updated, such that the default is now "*"
> for this property, and for all other service-specific proxyuser.*.groups
> properties in core-site.xml.
> Since not all environments include the "users" group, the "*" group is a more
> valid default value for this property. This change will also bring the
> Blueprint processor more closely in-line with the behavior of the UI, and so
> making the configuration more consistent across both options.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
