[
https://issues.apache.org/jira/browse/AMBARI-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-13379:
------------------------------------
Description:
*STR:*
# Install a cluster with atleast HDFS
# Open Add Service wizard
# Select Ranger service and partial set of services that is supported by
Ranger. Don't select few services that are supported by Ranger
# Go to Service configuration page -> Ranger service tab -> Ranger plugin smart
config tab
*Expected Result:* Services that are previously installed or selected to be
install, and supported by Ranger should have toggles for Ranger Plugin
*Actual Result:* Ranger Plugin for all services (even that are not installed or
selected to be install) that are supported by Ranger are visible
Also post installation on Ranger service configuration page, Ranger plugin
should be visible for only installed services
NOTE: As of Ambari-2.1.3 with HDP-2.3 stack: HDFS, YARN, KAFKA, KNOX, STORM,
HIVE and HBASE are the ranger supported services
*Fix:*
Added a resource property in config condition which defaults to config in
ambari-web, if not explicitly specified in a config condition.
It can be se to service when the *if* condition of a config needs to check
service state instead of a config value. As of now state attribute has not been
introduced and it's always presumed that service condition is for service being
installed or available int the cluster. In the future when required we can
introduce state attribute in config condition to support wider use cases
was:
*STR:*
# Install a cluster with atleast HDFS
# Open Add Service wizard
# Select Ranger service and partial set of services that is supported by
Ranger. Don't select few services that are supported by Ranger
# Go to Service configuration page -> Ranger service tab -> Ranger plugin smart
config tab
*Expected Result:* Services that are previously installed or selected to be
install, and supported by Ranger should have toggles for Ranger Plugin
*Actual Result:* Ranger Plugin for all services (even that are not installed or
selected to be install) that are supported by Ranger are visible
Also post installation on Ranger service configuration page, Ranger plugin
should be visible for only installed services
NOTE: As of Ambari-2.1.3 with HDP-2.3 stack: HDFS, YARN, KAFKA, KNOX, STORM,
HIVE and HBASE are the ranger supported services
> Ranger plugin toggles should be hidden for the services that are not
> installed or selected to get install
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-13379
> URL: https://issues.apache.org/jira/browse/AMBARI-13379
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13379.patch, Ranger Plugin.png
>
>
> *STR:*
> # Install a cluster with atleast HDFS
> # Open Add Service wizard
> # Select Ranger service and partial set of services that is supported by
> Ranger. Don't select few services that are supported by Ranger
> # Go to Service configuration page -> Ranger service tab -> Ranger plugin
> smart config tab
> *Expected Result:* Services that are previously installed or selected to be
> install, and supported by Ranger should have toggles for Ranger Plugin
> *Actual Result:* Ranger Plugin for all services (even that are not installed
> or selected to be install) that are supported by Ranger are visible
> Also post installation on Ranger service configuration page, Ranger plugin
> should be visible for only installed services
> NOTE: As of Ambari-2.1.3 with HDP-2.3 stack: HDFS, YARN, KAFKA, KNOX, STORM,
> HIVE and HBASE are the ranger supported services
> *Fix:*
> Added a resource property in config condition which defaults to config in
> ambari-web, if not explicitly specified in a config condition.
> It can be se to service when the *if* condition of a config needs to check
> service state instead of a config value. As of now state attribute has not
> been introduced and it's always presumed that service condition is for
> service being installed or available int the cluster. In the future when
> required we can introduce state attribute in config condition to support
> wider use cases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
