[
https://issues.apache.org/jira/browse/AMBARI-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546337#comment-14546337
]
Hudson commented on AMBARI-11153:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2613 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2613/])
AMBARI-11153. Configs: notes don't change if you navigate away (Richard Zang
via srimanth) (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a736f5ce6fbd97e7723f7c291a0928f93a7724a8)
* ambari-web/app/views/common/configs/config_history_flow.js
* ambari-web/app/mixins/common/configs/configs_saver.js
> Configs: notes don't change if you navigate away
> ------------------------------------------------
>
> Key: AMBARI-11153
> URL: https://issues.apache.org/jira/browse/AMBARI-11153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Richard Zang
> Assignee: Richard Zang
> Fix For: 2.1.0
>
> Attachments: AMBARI-11153.patch
>
>
> 1) Make a config change to HDFS
> 2) click save, enter note "FIRST CHANGE", save if fine and notes are saved
> 3) Make a config change to HDFS
> 4) Navigate away by clicking on YARN
> 5) You are prompted that you have unsaved changes, enter the notes "SECOND
> CHANGE" and save
> 4) the change is saved but the notes are not saved. It actually saves the
> notes as "FIRST CHANGE". So it used the previous note on this second config
> change.
> Seems any config change that is made based on navigating away always uses the
> last good config change thru normal edit/save.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
