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.

Description of problem:
Observed that sorting based on "Available" quantity on "All available subscriptions" tab is not sorting correctly

Version-Release number of selected component (if applicable):
subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.8.29-1
subscription-manager: 1.10.3-1.git.3.d610508.el7
python-rhsm: 1.10.3-1.git.0.6ac2883.el7


How reproducible:
4/4

Steps to Reproduce:
1.Register machine to candlepin server
2.Launch sub-man-gui
3.Move to "All available subscriptions"
4.Click on update ( with 'match my  system', 'have no overlap with existing subscriptions' selected)
5.sort based on the "Available" subscriptions 

Actual results:
Observed that the sorting is not working (PFA)

Expected results:
sorting based on the "Available" subscription should list the subscriptions based on the available subscriptions

Additional info:

observed that when less number of available subscriptions are present the sort is working as exepected, example list subscription for match installed products (say only 3 products are installed)

Created attachment 813194 [details]
ascendingorder

Created attachment 813195 [details]
descendingorder

I don't think this is a bug.  pools are sorted by the parent node first (for stacks this is blank in the available field).  It's not particularly useful this way, but there's not much we can do, and I don't think changing it would expose more information, or make it easier to use.