Created attachment 1731306 [details] search_filterByLabel Description of problem: When searching for a label on the Search Page (using the top search for label bar), it does not apply my selection to the resources I have selected. Version-Release number of selected component (if applicable): 4.7.0-0.nightly-2020-11-18-085225 In my case, I used the Pipeline Operator (version doesn't matter, but I was on 1.2.0 - preview channel). How reproducible: Always Steps to Reproduce: 1. Go to Search 2. Select a resource 3. Filter for a label that matches 3a. I used Pipelines, so I filtered on "pipeline.openshift.io/runtime=nodejs" Actual results: The top filter component does not impact the selected resources The selected resources have a label selection, and that works. Expected results: Top filter to apply the filter to all selected resources (I would think, given that's how the name filter works) Additional info:
Created attachment 1731318 [details] Search_filterByName Adding the Search_filterByName gif. This showcases a similar problem with name filtering in the top bar, but oddly slightly different in that it applies the search to the selected resource.
Created attachment 1731325 [details] Search - Filter in Resource Section, filter by label displays possible labels tooltip and filters correctly
Created attachment 1731326 [details] Search - Top Filter, filter by label doesn't filter resources
fix is not included in 4.7.0-0.nightly-2020-11-26-201843 yet
Tested against pr: https://github.com/openshift/console/pull/7318. On search page, filter "Pipelines" resource, now there is only top level name/label filter, and filter by label, could filter out expected pipelines.
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633