← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1398695] [NEW] [sahara] node group template shows redundant process tab

 

Public bug reported:

When we want to edit process configurations in Horizon. For example, we add a "Namenode" process in CDH plugin, we suppose we will only have "NAMENODE" tab shown in this page besides the "Create Node Group Template" tab. However, we will have two tabs shown instead one. They are "NAMENODE" and "SECONDARYNAMENODE". The reason is in nodegroup_templates.html, function get_service_tab is defined as:
            function get_service_tab(service) {
                return $("a").filter(function (idx, e) {
                    return $(e).attr("data-target") && $(e).attr("data-target").indexOf(service.toLowerCase()) != -1
                }).closest("li");
            }
by this way it will get all names including "NAMENODE" instead of precise matching. This behavior is confusing and not desired, and we need to replace it by precise matching.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1398695

Title:
  [sahara] node group template shows redundant process tab

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When we want to edit process configurations in Horizon. For example, we add a "Namenode" process in CDH plugin, we suppose we will only have "NAMENODE" tab shown in this page besides the "Create Node Group Template" tab. However, we will have two tabs shown instead one. They are "NAMENODE" and "SECONDARYNAMENODE". The reason is in nodegroup_templates.html, function get_service_tab is defined as:
              function get_service_tab(service) {
                  return $("a").filter(function (idx, e) {
                      return $(e).attr("data-target") && $(e).attr("data-target").indexOf(service.toLowerCase()) != -1
                  }).closest("li");
              }
  by this way it will get all names including "NAMENODE" instead of precise matching. This behavior is confusing and not desired, and we need to replace it by precise matching.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1398695/+subscriptions


Follow ups

References