Hide Forgot
Description of problem: In "Manage Repositories" dialog, the only column where sorting works is "Modified" - "Enabled" and "Gpgcheck" are not activable, and Repository is activable, but does not produce any change, and the lines stays disordered. Version-Release number of selected component (if applicable): subscription-manager-gui-1.17.11-1.el7.x86_64 subscription-manager-1.17.11-1.el7.x86_64 How reproducible: reliably Steps to Reproduce: 1. subscription-manager-gui 2. open Repositories Management windows 3. try to sort by different columns Actual results: Enabled - is not clickable Gpgcheck - is not clickable Repository - is clickable, but has no effect on the item order Modified - works Expected results: Enabled - Works Gpgcheck - Works Repository - Works Modified - works Additional info:
I have added gui test for this behaviour. See external trackers.
*** Bug 1378927 has been marked as a duplicate of this bug. ***
*** Bug 1380725 has been marked as a duplicate of this bug. ***
Created attachment 1268885 [details] Can be sorted by Modified
Created attachment 1268886 [details] Sorted by repo id
The fix that went in for this in the PR addressed an issue where columns that should have been sorting were not. Sorting additional columns would be a new feature request, (please open an RFE for that if desired). So as of this bug fix: Expected results: Enabled - Not clickable Gpgcheck - Not clickable Repository - Sortable Modified - Sortable
For posterity - Repository column was the important one to me, so I'm ok with the resolution.
marking bug as verified!! [root@dhcp70-137 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.9.51.21-1 subscription management rules: 5.15.1 subscription-manager: 1.19.4-1.el7 python-rhsm: 1.19.2-1.el7
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/RHBA-2017:2083