[
https://issues.apache.org/jira/browse/AMBARI-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597840#comment-14597840
]
Hadoop QA commented on AMBARI-12092:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12741303/AMBARI-12092.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/3239//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3239//console
This message is automatically generated.
> Strange behavior after discarding changes in compare mode
> ---------------------------------------------------------
>
> Key: AMBARI-12092
> URL: https://issues.apache.org/jira/browse/AMBARI-12092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12092.patch
>
>
> STR:
> 1. Install Ambari.
> 2. Go to config page for some service.
> 3. Make some change and save them to create new version.
> 4. Compare current version with other one.
> 5. Change some config in compare mode (not sure if it is expected to allow to
> change configs in compare mode)
> 6. Discard changes.
> After these actions all configs wll be loaded (so it is not comparing mode),
> but comparing bar still shows, that we are comparing two versions.
> Configs should not be editable in compare mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
