Red Hat Bugzilla – Bug 1092609
Searching for objects that _do not_ have a tag in the search bar is not possible
Last modified: 2016-02-10 14:17:18 EST
Description of problem: While searching for objects that do have a specific tag in the search bar is possible (e.g. "Vms: tag = tag1") searching for objects that do not have a tag is not possible (e.g. "Vms: tag != tag1" returns nothing). Version-Release number of selected component (if applicable): rhevm-webadmin-portal-3.3.2-0.50.el6ev How reproducible: Always Steps to Reproduce: 1. Create two tags "tag1" and "tag2". 2. Assign "tag1" to vm1 and "tag2" to vm2. 3. Search for "Vms: tag != tag1" in the search bar. Actual results: Nothing is displayed. Expected results: At least vm2 is displayed. Additional info: Searching with != operator is possible for other properties such as Name (e.g. "Vms: name != vm1").
Created attachment 897468 [details] screenshot showing that this is an unsupported operation
Please note that this operation is not supported currently as shown in the attached screen shot. If you think that this is a mandatory operation, you should open a RFE
(In reply to Eli Mesika from comment #2) > Please note that this operation is not supported currently as shown in the > attached screen shot. > If you think that this is a mandatory operation, you should open a RFE As per "F.3.6. Searching for Objects Using Tags" section of the Administration Guide: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html/Administration_Guide/To_search_for_objects_using_tags.html <quote> See Also: Section F.1, “Search” </quote> As per table "Table F.3. Example Search Criteria" in section "F.1.5. Search Criteria": https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html/Administration_Guide/appe-Using_Search_Bookmarks_and_Tags_to_Find_Your_Way_Around.html#Search_criteria <quote> operator Comparison operators. = != (not equal) > < >= <= -- Value options depend on obj-type. </quote> Please fix the search or fix the documentation.
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://rhn.redhat.com/errata/RHSA-2015-0158.html