[
https://issues.apache.org/jira/browse/AMBARI-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598067#comment-14598067
]
Hudson commented on AMBARI-12092:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2981 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2981/])
AMBARI-12092 Strange behavior after discarding changes in compare mode.
(ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aa170c033452c3e331ea1e7311aa88997337845c)
* ambari-web/app/views/common/configs/config_history_flow.js
* ambari-web/app/mixins/common/configs/configs_loader.js
* ambari-web/app/mixins/common/configs/configs_comparator.js
> 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)
