Reviewed: https://review.openstack.org/269772 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=94c4f7b3d011168f44cf8e62bdb15f4a02edfed7 Submitter: Jenkins Branch: master
commit 94c4f7b3d011168f44cf8e62bdb15f4a02edfed7 Author: Justin Pomeroy <[email protected]> Date: Tue Jan 19 10:52:25 2016 -0600 Fix metadata tree available filter This patch updates the filtering of the available metadata items in the Update Metadata modal so that any leaf with either a display value or property name that matches will be displayed. Parent items of any matching leaf are also displayed so context and the tree structure are preserved. Closes-Bug: #1519535 Closes-Bug: #1519567 Closes-Bug: #1463733 Change-Id: I11caf506a851807cb3b079184dd260db6862b3d9 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1519535 Title: Update image metadata - filtering is not reliable Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Noticed in cirros image (uploaded by devstack), demo user: I've tried to type "CPU" to filter field by Available metadata column and among valid names as 'CPU Pinning' or 'Max vCPU Cores' there is also 'Guest Memory Backing'. Another example by bassing 'drive' there are also 'CPU Pinning', 'Virtual CPU Topology', 'Watchdog Behavior', 'Disk Adapter Type' or 'OS Type'. The list of false-matching names is not complete at all, but I hope it's sufficient to describe situation. Used environment: devstack (latest commit has Change-Id: I0e102b671f03ccb183d30ec6a762d00ebcf1e4b5), default conf. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1519535/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
