[
https://issues.apache.org/jira/browse/AMBARI-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544859#comment-14544859
]
Hadoop QA commented on AMBARI-11153:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12733041/AMBARI-11153.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2735//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2735//console
This message is automatically generated.
> 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)
