Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 29 Aug 2014 11:26:53 +0000 (UTC)
From: "Andrii Tkach (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12737775.1409311608381.1505.1409311613422@arcas>
In-Reply-To: <JIRA.12737775.1409311608381@arcas>
References: <JIRA.12737775.1409311608381@arcas>
Subject: [jira] [Created] (AMBARI-7074) Config History: unable to display a
 service config version in non-default group
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andrii Tkach created AMBARI-7074:
------------------------------------

             Summary: Config History: unable to display a service config version in non-default group
                 Key: AMBARI-7074
                 URL: https://issues.apache.org/jira/browse/AMBARI-7074
             Project: Ambari
          Issue Type: Task
          Components: ambari-web
    Affects Versions: 1.7.0
            Reporter: Andrii Tkach
            Assignee: Andrii Tkach
            Priority: Critical
             Fix For: 1.7.0


See the attached video for the current behavior (which is incorrect).

* On HDFS > Configs page, 'hdfs111' config group is selected. 
* This shows all SCVs that belong to 'hdfs111' config group in white boxes, and SCVs that belong to the default config group in gray boxes (expected behavior).
* Click on V10 (this belongs to 'hdfs111' group).  The config group pulldown should remain 'hdfs111' and display the contents of V10 and highlight the V10 box.  However, this is not working currently.

Possible reason:
* In configs controller, we always load selected servcie config version first, then load Tags and Groups


--
This message was sent by Atlassian JIRA
(v6.2#6252)