Bug 1517392 - [REGRESSION] Search VM/Instance stopped working
Summary: [REGRESSION] Search VM/Instance stopped working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.10.0
Assignee: Martin Povolny
QA Contact: Matouš Mojžíš
URL:
Whiteboard: regression:ui
: 1509318 (view as bug list)
Depends On:
Blocks: 1520667
TreeView+ depends on / blocked
 
Reported: 2017-11-24 19:56 UTC by Leo Khomenko
Modified: 2019-08-06 20:05 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1520667 (view as bug list)
Environment:
Last Closed: 2018-06-21 20:42:31 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
search results (100.46 KB, image/png)
2017-11-24 19:56 UTC, Leo Khomenko
no flags Details

Description Leo Khomenko 2017-11-24 19:56:18 UTC
Created attachment 1358773 [details]
search results

Description of problem: search doesn't filter anything


Version-Release number of selected component (if applicable):5.9.0.10


How reproducible:100%


Steps to Reproduce:
1.open Compute/Cloud(Infra)/Instances(or Vms)
2.Use searchbox to filter VMs

Actual results:all VMs are showm


Expected results:only filtered VMs should stay

Comment 2 Milan Falešník 2017-11-27 16:27:31 UTC
We have identified the reproduction sequence together with mpovolny:

1. Have a fresh browser, then go to Compute/Infra/Virtual Machines, then the VMs accordion
2. Search for anything. The search works as expected here.
3. Click on any of the resulting VMs to open its details.
4. Then click on the root node of the tree in the VMs accordion (All VMs) to go back to the display of multiple VMs quadicons.
5. Then try searching anything else.

The bug occurs.

Comment 5 Hilda Stastna 2017-12-04 10:09:54 UTC
*** Bug 1509318 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.