You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2014/08/04 18:54:12 UTC
[jira] [Resolved] (AMBARI-6733) Could not change values in
storm-env.sh from UI
[ https://issues.apache.org/jira/browse/AMBARI-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitaly Brodetskyi resolved AMBARI-6733.
---------------------------------------
Resolution: Fixed
Committed to trunk
> Could not change values in storm-env.sh from UI
> -----------------------------------------------
>
> Key: AMBARI-6733
> URL: https://issues.apache.org/jira/browse/AMBARI-6733
> Project: Ambari
> Issue Type: Bug
> Components: agent
> Affects Versions: 1.7.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-6733.patch
>
>
> Precondition:
> Deploy ambari with all services and default settings
> BUT
> Change storm-env.sh content at installer step (add '111' in text area)
> STR:
> 1)Navigate on Services->Storm tab->configs
> 2)Check storm-env.sh content value
> 3)Check /etc/storm/conf.dist/storm-env.sh file
> 4)Change storm-env.sh content value once more (Save and restart all components that need it)
> 5)Check /etc/storm/conf.dist/storm-env.sh file
> Expected result:
> File /etc/storm/conf.dist/storm-env.sh and field storm-env.sh content have same value.
> Actual result:
> File /etc/storm/conf.dist/storm-env.sh and field storm-env.sh content are independent of each other.
--
This message was sent by Atlassian JIRA
(v6.2#6252)