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:
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
Our auto suggestion mechanism in the UI actually suggest these as valid search options.
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.
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)
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
Verified in RHEVM version 4.2.0-0.6.el7. Tested with: tag="tag1" and "tag2" Result: Correct VMs are shown.
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
BZ<2>Jira Resync