RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 668572 - Filters do not behave as expected
Summary: Filters do not behave as expected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: J.C. Molet
URL:
Whiteboard:
Depends On:
Blocks: Entitlement-Beta
TreeView+ depends on / blocked
 
Reported: 2011-01-10 20:00 UTC by J.C. Molet
Modified: 2013-01-10 10:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:38:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0611 0 normal SHIPPED_LIVE new package: subscription-manager 2011-05-18 17:56:21 UTC

Description J.C. Molet 2011-01-10 20:00:31 UTC
Description of problem:
When logging in as one of the rh-alpha-* users on the dev2 server, I cannot seem to predict how my search results will look.  This should be simple as there are only two subscriptions that both match your hardware. 

Version-Release number of selected component (if applicable):
subscription-manager-firstboot-0.93.10-1.git.4.433f1bd.el6.x86_64
subscription-manager-gnome-0.93.10-1.git.4.433f1bd.el6.x86_64
subscription-manager-0.93.10-1.git.4.433f1bd.el6.x86_64

Steps to Reproduce:
1.  install rhsm-gui and all required deps
2.  register as one of the rh-alpha-* users on dev2 (i used rh-alpha-152)
3.  Search for subscriptions toggling the check boxes
4.  Register to one of the subs
5.  Search again, toggling the check boxes
  
Actual results:
There are two subscriptions in here.  I can toggle between viewing the two by checking/unchecking "match my hardware".  Both of these subscriptions should match my hardware. 

Expected results:
When "match my hardware" is checked, both subscriptions should show.

Additional info:
It might be more intuitive if these check boxes behaved as filters as opposed to toggle switches.  Doing it this way, all of your subscriptions for a user would be shown by default and then the list would be narrowed down by applying the filters.

Regardless of the above suggestion, the current switches seem broken.

Comment 1 James Bowes 2011-01-19 18:43:02 UTC
'match my hardware' is a misnomer, the operation is actually looking for pools that your system would pass a rules check for when you subscribe to them. I think the original text for this tick box was 'are applicable to my system'.

Once you have subscribed to a pool, further attempts to subscribe to that pool will fail (since you can only grab one entitlement from a pool). That pool is then no longer applicable to your system, which is why toggling match my hardware makes it appear and disappear.

When we have pools/products with the multi-entitle attribute, for which you're allowed to grab more than one entitlement, this logic is no longer applicable. it will always show up as being applicable to your system, and thus 'match your hardware'

What i'd like to do is take any pools that are not applicable to the system, but for which you have a subscription, and remove them from the results entirely. This should keep the multi-entitle pools as still being visible and matching your hardware, and prevent any pools that you're already subscribed to from jumping to different places in the ui.

Comment 2 James Bowes 2011-01-25 20:19:56 UTC
I've implemented the above (removing already installed pools from the results). I've also turned the check boxes into real filters, so when checked they remove results, but when unchecked they do nothing (rather than adding in different ones). Further changes to clean up the UI are forthcoming

Comment 4 J.C. Molet 2011-01-26 16:25:33 UTC
The search criteria behaves as filters now, and it is much easier to predict the outcome of searches.  The filters have been verified that they behave correctly as well.

subscription-manager-gnome-0.93.15-1.git.2.483e1d2.el6.x86_64
subscription-manager-0.93.15-1.git.2.483e1d2.el6.x86_64
subscription-manager-firstboot-0.93.15-1.git.2.483e1d2.el6.x86_64

Comment 5 errata-xmlrpc 2011-05-19 13:38:44 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0611.html


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