Description of problem: Sorting of available minor version repos is not consistent. Example: When we look for "Red Hat Enterprise Linux 7 Server (RPMs)" repos we see "x86_64 7Server" as a first entry. Whereas when we look for "Red Hat Enterprise Linux 6 Server (RPMs)" repos then we see "x86_64 6Server" as the last entry and the sorting is like: i386 6.1 x86_64 6.1 x86_64 6.10 <<<< After 6.1 we should see 6.2 instead of 6.10 i386 6.10 i386 6.2 x86_64 6.2 i386 6.3 ... ... ... x86_64 6Server i386 6Server 6Server or 7Server are base repositories and these are most commonly used repos so those should be listed as a first entry.
In this example, 7Server is listed at the top but the sorting is still disordered: Red Hat Enterprise Linux OpenStack Platform 7.0 director for RHEL 7 (RPMs) rhel-7-server-openstack-7.0-director-rpms x86_64 7Server x86_64 7.2 x86_64 7.3 x86_64 7.0 x86_64 7.1 x86_64 7.4 x86_64 7.5
Created redmine issue https://projects.theforeman.org/issues/24679 from this bug
Upstream bug assigned to micjohns
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24679 has been resolved.
Michael, This failed cherrypick downstream. Can you take a look?
Hello Ashish, Here's what you can expect from the sorting now: repositories will be sorted in descending order, grouped by architecture. Also, any non y-stream repo (ie 7Server) will be moved to the top as we want to encourage use of those rather than y-stream repositories. Something like this: x86_64 6Server i386 6Server x86_64 6.10 x86_64 6.9 .... i386 6.10 i386 6.9
Thank you Johathon for the update and considering this for GA.
snap 23, not 63
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/RHSA-2018:2927
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days