Bug 1343707 - Drop down menu for composite content view versions are not sorted
Summary: Drop down menu for composite content view versions are not sorted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.1.8
Hardware: x86_64
OS: Linux
low
low
Target Milestone: 6.7.0
Assignee: Nagoor Shaik
QA Contact: Peter Dragun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-07 18:00 UTC by David Wood
Modified: 2021-12-10 14:40 UTC (History)
14 users (show)

Fixed In Version: tfm-rubygem-katello-3.14.0.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-14 13:22:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen shot of issue (18.45 KB, image/png)
2016-06-07 18:00 UTC, David Wood
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16333 0 Normal Closed Drop down menu for composite content view versions are not sorted 2020-04-20 04:14:57 UTC
Red Hat Knowledge Base (Solution) 3264581 0 None None None 2017-12-06 23:36:51 UTC
Red Hat Product Errata RHSA-2020:1454 0 None None None 2020-04-14 13:22:44 UTC

Description David Wood 2016-06-07 18:00:44 UTC
Created attachment 1165725 [details]
Screen shot of issue

Description of problem:
The drop down menu for composite content view versions are not sorted in numerical order

Version-Release number of selected component (if applicable):
6.1.8

How reproducible:
Always

Steps to Reproduce:
1. Create 76 versions of a content view
2. View the drop down of versions on the Composite Content View Build page

Actual results:
The versions are not sorted numerically

Expected results:
The versions should be sorted numerically

Additional info:
Attached is a screen shot of the issue.  The sorting is correct on the list of versions but on drop down menus, they are not.

Comment 2 Brad Buckingham 2016-08-26 13:24:07 UTC
Created redmine issue http://projects.theforeman.org/issues/16333 from this bug

Comment 8 Bryan Kearney 2018-09-04 18:02:23 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 9 Nagoor Shaik 2019-10-18 13:50:22 UTC
Patch fix available for this issue now https://github.com/Katello/katello/pull/8392. Re-opening this Bug.

Comment 10 Bryan Kearney 2019-10-21 14:00:21 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/16333 has been resolved.

Comment 11 Lukas Pramuk 2019-12-10 16:07:37 UTC
FailedQA.

@Satellite 6.7.0 Snap5
tfm-rubygem-katello-3.14.0-0.4.rc2.el7sat.noarch

used the manual reproducer described in comment#0

1. Create 12 versions of a Content View
2. View the drop down of versions on the Composite Content View Build page

Satellite 6.6.0 (reproducer):
Always Use Latest (Currently 12.0)
12.0
11.0
9.0
6.0
5.0
2.0
10.0
8.0
7.0
4.0
3.0
1.0

>>> reproduced, dropdown items are not sorted

vs.

Satellite 6.7.0 Snap5 (fix):
Always Use Latest (Currently 12.0)
9.0
8.0
7.0
6.0
5.0
4.0
3.0
2.0
12.0
11.0
10.0
1.0

>>> failed, dropdown items are sorted *alphabetically* (should be numerically instead)

Comment 12 Nagoor Shaik 2019-12-11 12:33:01 UTC
This seems to be a problem sorting the CCV based on the version, new patch is sent upstream for review https://github.com/Katello/katello/pull/8473

Comment 13 Brad Buckingham 2019-12-16 18:47:13 UTC
Moving back to post based upon the new PR being merged upstream.

Comment 15 Peter Dragun 2020-01-16 11:00:31 UTC
Verified on Satellite 6.7 snap 8 using manual reproducer with 30 versions of content view. 
Versions are sorted correctly in numerical order.

Comment 19 errata-xmlrpc 2020-04-14 13:22:16 UTC
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-2020:1454


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