Bug 1056502 (RHEV_Search_by_multiple_tags)

Summary: [RFE] Allow to filter by more than one tag
Product: Red Hat Enterprise Virtualization Manager Reporter: Ulhas Surse <usurse>
Component: ovirt-engineAssignee: Alexander Wels <awels>
Status: CLOSED ERRATA QA Contact: samuel macko <smacko>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: bgraveno, emesika, gshereme, lsurette, lsvaty, mgoldboi, mlipchuk, mperina, nbarcet, pdwyer, pnovotny, pstehlik, rbalakri, Rhev-m-bugs, srevivo, usurse, ykaul, ylavi
Target Milestone: ovirt-4.2.0Keywords: FutureFeature
Target Release: ---Flags: sherold: Triaged+
lsvaty: testing_plan_complete-
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
This update allows you to search in Red Hat Virtualization Manager using more than one tag.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-15 17:36:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1450749    
Bug Blocks:    

Description Ulhas Surse 2014-01-22 10:40:31 UTC
Description of problem:
VM is not searchable when searching with tags rhevm: (Vms: tag = XXX and tag = YYY)

Version-Release number of selected component (if applicable):
rhevm-3.2.3-0.43.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1) Select two tags for which there is at least one VM with both tags.
2) Search for VMs having both tags (Vms: tag = XXX and tag = YYY)
3) An empty list is returned rather than the list of all VMs having both tags.

Actual results:
Blank output, no VM's listed.

Expected results:
VM's with searched field must be listed

Additional info:

Comment 2 Eli Mesika 2014-01-25 21:49:11 UTC
AFAIK it is not a supported operation since the query is translated at last to SQL it means that the condition is checked on each record in the result set.

Lets say that you have 2 VMs one is named VM1 and the other VM2
Now
Its clear that if you issue a query with name='VM1' and name = 'VM2' , you will got empty result 
The same is for tags , each record in the result set have either 'win7' or 'windows' value , there is no record that has both
If you will look under teh system tree you can see that you can manage Tags there as well but you can not select more than one tag to display

Comment 9 Arthur Berezin 2014-02-05 19:07:06 UTC
Our auto suggestion mechanism in the UI actually suggest these as valid search options.

Comment 15 Ulhas Surse 2014-11-03 09:05:42 UTC
Hello team,
Does that mean the feature can't be included? As per comment 2, it is not supported and seems true with the logic. 

I just want to know is there any thought going behind the bugzilla? Can you please share the current progress.

Comment 19 Pavel Novotny 2016-10-11 12:53:42 UTC
FYI, still reproducible in rhevm-4.0.5-0.1.el7ev. 

Example: 
VMs: vm01 (tags: tag1,tag2)
     vm02 (tags: tag2)
     vm03 (tags: -)

Query "Vms: tag = tag1 or tag = tag2" returns vm01, vm02
Query "Vms: tag = tag1 and tag = tag2" returns nothing (should return vm01)

Comment 28 RHV bug bot 2017-12-06 16:17:58 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 29 samuel macko 2017-12-08 12:42:55 UTC
Verified in RHEVM version 4.2.0-0.6.el7.

Tested with:
  tag="tag1" and "tag2"

Result:
  Correct VMs are shown.

Comment 30 RHV bug bot 2017-12-12 21:16:27 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 33 errata-xmlrpc 2018-05-15 17:36:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1488

Comment 34 Franta Kust 2019-05-16 13:07:09 UTC
BZ<2>Jira Resync