[
https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390797#comment-15390797
]
Sumit Mohanty commented on AMBARI-17861:
----------------------------------------
[~harsha_ch] you are right that this property may not be available in
cluster-env and it looks to me that the property may not be in cluster-env at
all if the user does not explicitly add it.
See
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py#L145
and it shows how the property is read from ambari.properties file and
optionally from cluster-env.
It seems to me that the the place to add this logic is in stack advisor only.
Another reason is that the property being modified is {{nimbus.admins}} and if
its not done via stack advisor user will not see its final value and that can
be confusing.
Let me reopen this JIRA.
> Ambari principal should be part of nimbus.admins for Storm View
> ---------------------------------------------------------------
>
> Key: AMBARI-17861
> URL: https://issues.apache.org/jira/browse/AMBARI-17861
> Project: Ambari
> Issue Type: Bug
> Reporter: Sriharsha Chintalapani
> Assignee: Sriharsha Chintalapani
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17861-II.patch, AMBARI-17861.addendum.patch,
> AMBARI-17861.patch, AMBARI-17861.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
