yahoo-eng-team team mailing list archive

[Julie Gravel <julie.gravel@xxxxxx>]

Public bug reported:

Currently if there's a property that appears in more than one namespace
(hence non-unique) and the user selects that property from one of the
namespace, the Metadata widget will remove it from only one of the
namespaces.  When the user reloads the widget, it will just remove that
property from whichever namespace it processes first while other
namespaces will still display the property.

Having the same property in different namespaces is a possible scenario
for Cinder's volume type extra specs where there is no guarantee that
different drivers will use unique extra spec keys.

The widget should remove the property from ALL namespaces after the user
selects it. This is so that the same property will not show up again in
other namespaces after a reload.

** 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/1400568

Title:
  Metadata widget should deal with non-unique properties

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Currently if there's a property that appears in more than one
  namespace (hence non-unique) and the user selects that property from
  one of the  namespace, the Metadata widget will remove it from only
  one of the namespaces.  When the user reloads the widget, it will just
  remove that property from whichever namespace it processes first while
  other namespaces will still display the property.

  Having the same property in different namespaces is a possible
  scenario for Cinder's volume type extra specs where there is no
  guarantee that different drivers will use unique extra spec keys.

  The widget should remove the property from ALL namespaces after the
  user selects it. This is so that the same property will not show up
  again in other namespaces after a reload.

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